11–20 of 62 posts
The Great Suspender is a great plugin to achieve this.
This looks nice! As I enabled it, I got the normal warning about "This plugin can view all data" etc, and I started looking for a plugin that can show me what servers plugins are connecting to... it seems there is no such thing. Perhaps time to re-enable little snitch.
I wouldn't mind having my background Netflix just stop, or having to wait a few secs for an interval refresh after bringing a tab to front.
But seeing as this seems an active area of research and debate I have a feeling that this solution has drawbacks I'm not considering...
How much benefit is there in doing anything at all on a background tab? Would there be many use cases where simply suspending the background tab threads would lead to a much worse user experience? I wouldn't mind having my background Netflix just stop, or having to wait a few secs for an interval refresh after bringing a tab to front. But seeing as this seems an active area of research and debate I have a feeling tha…
Even consider the typical hackernews demo of a javascript genetic algorithm: you probably want to be able to leave it to run for a while while you do other things without being required to keep the tab visible.
How much benefit is there in doing anything at all on a background tab? Would there be many use cases where simply suspending the background tab threads would lead to a much worse user experience? I wouldn't mind having my background Netflix just stop, or having to wait a few secs for an interval refresh after bringing a tab to front. But seeing as this seems an active area of research and debate I have a feeling tha…
Even consider the typical hackernews demo of a javascript genetic algorithm: you probably want to be able to leave it to run for a while while you do other things without being required to keep the tab visible.
>Tabs playing audio or maintaining real-time connections like WebSockets or WebRTC How long before a "performance best practices" guide suggests leaving a websocket open to ensure snappier page responses when users switch to your tab.
I had a similar thought. I think browsers should require user permission for a tab to use more than 1% of a core on average.
I think it would be better to give each tab a power budget that, initially, allows it to run for S seconds at full power, and that give it new budget at a rate of x However, I fear that still won't be enough. The list of heuristics and exceptions could get so long that the resulting benaviour becomes difficult to explain.
How much benefit is there in doing anything at all on a background tab? Would there be many use cases where simply suspending the background tab threads would lead to a much worse user experience? I wouldn't mind having my background Netflix just stop, or having to wait a few secs for an interval refresh after bringing a tab to front. But seeing as this seems an active area of research and debate I have a feeling tha…
There are use cases such as a webmail client still fetching messages so it can notify (e.g. via browser tab icons), or so that a collaborative editor keeps up with changes. Even consider the typical hackernews demo of a javascript genetic algorithm: you probably want to be able to leave it to run for a while while you do other things without being required to keep the tab visible.
>Tabs playing audio or maintaining real-time connections like WebSockets or WebRTC How long before a "performance best practices" guide suggests leaving a websocket open to ensure snappier page responses when users switch to your tab.
How much benefit is there in doing anything at all on a background tab? Would there be many use cases where simply suspending the background tab threads would lead to a much worse user experience? I wouldn't mind having my background Netflix just stop, or having to wait a few secs for an interval refresh after bringing a tab to front. But seeing as this seems an active area of research and debate I have a feeling tha…
There are use cases such as a webmail client still fetching messages so it can notify (e.g. via browser tab icons), or so that a collaborative editor keeps up with changes. Even consider the typical hackernews demo of a javascript genetic algorithm: you probably want to be able to leave it to run for a while while you do other things without being required to keep the tab visible.
A big factors seems to be that the pages that are built out of layers of active advertising devices - a given advertiser isn't concerned that they're one of ten monetizing devices pasted onto a gvien page.
And there's the way pages have disincentive to play nice - a page that barely works with only it open trains users to avoid other pages.
How much benefit is there in doing anything at all on a background tab? Would there be many use cases where simply suspending the background tab threads would lead to a much worse user experience? I wouldn't mind having my background Netflix just stop, or having to wait a few secs for an interval refresh after bringing a tab to front. But seeing as this seems an active area of research and debate I have a feeling tha…
Otherwise, each time you switched tabs to your spreadsheet, doc, slide show, etc., it would have to poll for changes from the server in some fashion, and wait for a response. This gets pretty frustrating when you're trying to do something like copy from one document to another.