5 ms·
> It's a hard problem as web developers have incentive to use all the horsepower available to them. Although it's not only the fault of the browser devs, but p
by dom0 10y ago
> It's a hard problem as web developers have incentive to use all the horsepower available to them.
Although it's not only the fault of the browser devs, but probably mainly of JS/frontend devs... the result is that leaving a browser window open easily halves battery time, because even innocuous sites eat half a core of CPU. Also, fan's always whirling.
Qubes OS is quite nice here. Just pause the VM with the browser in it -> 0 % CPU, but can still read what's on the display.
- technomancy 10y ago> Just pause the VM with the browser in it -> 0 % CPU, but can still read what's on the display. On a related note, how is "halt all execution and scheduled future execution of scripts in the current tab" not a solved problem for mainstream browsers? Or maybe it is and somehow I missed it?
- caf 10y agoI'd be happy with "tabs not visible go into stasis".
- angry-hacker 10y agoVivaldi hibernates background tabs natively. Can't remember the details. There are extensions, but they just swap the site with static page.
- jmiserez 10y agoThere are some FF extensions that do just that, but some sites break as they're not expecting it.
- caf 10y agoWouldn't those same sites break in exactly the same way if you were browsing them on a mobile browser and switched temporarily away to another app? Or suspended/resumed your desktop?
- vthriller 10y agoNot exactly that, but with Firefox you can tweak dom.min_background_timeout_value so scripts in the background tabs could be invoked even less often than they already are. (Chrome does the same, but its minimal timeout value is, unfortunately, hard-coded.)
- technomancy 10y agoFantastic; thanks!