3 ms·
This doesn't seem like it should be built in at the browser level. The brower's job should be to process requests and render webpages as quickly as possible. If
by jjordan 9y ago
This doesn't seem like it should be built in at the browser level. The brower's job should be to process requests and render webpages as quickly as possible. If a user wants to intervene in that process, that is their prerogative, but it definitely should remain at the plugin level.
- bzbarsky 9y agoI agree the browser's job should be to process requests as quickly as possible. If the web page asks for 150 scripts to be loaded (e.g. that's what https://www.nytimes.com https://www.nytimes.com does right now), what is the fastest way to load them? "All in parallel" is not the right answer, so you end up prioritizing. At that point, maybe you want to prioritize the 40 non-tracking scripts (how many get loaded if I enable tracking protection in Firefox on that site) over the 110 tracking ones.