|
|
|
|
|
by hdjjhhvvhga
1669 days ago
|
|
This is my pet peeve. Browsers should not allow any websites to hijack all computing cycles. This was already clear a few years ago during the Monero hype. The fact that most adblockers will detect such attempts today doesn't change the fact that any website can almost prevent you from doing other work just because you opened it. The current strategy of dealing with this problem ("this tab has become unresponsive") is inadequate because it is reactive, not proactive. I'd like to be able to blacklist everything and whitelist only chosen websites I trust. Loading for too long because of tracking code? Too bad, choose another loading strategy or I just close the tab. Making my fans spin faster? Begone. |
|
1.) A subset of modern HTML / CSS, custom Javascript. Remove anything that isn't needed and especially anything that affects rendering negatively for no good reason.
1.1.) Possibly: Provide versioned, vendor neutral versions of js to allow for autocomplete.
2.) Same as 1, but with custom JS. All js must complete in a specified number of cycles. User interaction gives extra cycles.
The point of 1 is to:
- for companies: massively lower the barriers for new browsers (remove lots of backwards compatibility and the huge problem of JS)
- for security conscious users: provide a safer way to browse the web
- for users generally: provide a way to browse the web faster and more comfortably
- the point of 2.) is to provide an approximation of what we have today but in a way that automatically limits developers from abusing JS.