I pretty much always have >200 tabs open, and it sometimes gets up to more like 1000. (Currently I have about 100 windows open, some of them with dozens of tabs.)
Works fine in Safari, somewhat in Firefox, but Chrome chokes and falls to pieces.
The easy short-term fix to this problem is: stop using Chrome and switch to a different browser. The medium-term solution is to improve the way Chrome handles resources for heavy browsing workloads.
Running every webpage on a remote server is a ridiculous response.
All the browsers could still be better with these kinds of workloads though. Someone working on browsers should spend a few months or years considering how to suspend and cut off system resources to background tabs, make sure no browser tasks are accidentally quadratic in number of tabs or windows, etc.
Why is running every webpage on a remote server a ridiculous response? I don't really care what the software is doing as long as (/if) it solves my problem. I agree switching to a different browser is the easy short term fix, but that might not work for some people. The medium-term solution is not really a response because that's completely out of your control.
I mean the medium-term response from someone who wants to make it their full-time work project to solve this problem for everyone. For someone who doesn’t have the political clout to change Chrome directly, a plugin or fork could probably also be made to solve the problem.
Personally what I’d like to see in a browser is a more explicit and configurable policy about how many resources to devote to background tabs.
The remote-execution solution is incredibly bandwidth-heavy, costs money, hands all browsing data over to a third party, creates an unnecessary dependency on a startup company that might fail or get bought at any time, and takes a ton of control out of end-users’ hands.
I highly doubt a plugin would work, but maybe a fork could work. It does seem like Mighty is collaborating with the Chrome team to make improvements to Chrome directly: https://twitter.com/Suhail/status/1385237770633846784
>creates an unnecessary dependency on a startup company that might fail or get bought at any time
This is the story of any new company trying to build anything
Works fine in Safari, somewhat in Firefox, but Chrome chokes and falls to pieces.
The easy short-term fix to this problem is: stop using Chrome and switch to a different browser. The medium-term solution is to improve the way Chrome handles resources for heavy browsing workloads.
Running every webpage on a remote server is a ridiculous response.
All the browsers could still be better with these kinds of workloads though. Someone working on browsers should spend a few months or years considering how to suspend and cut off system resources to background tabs, make sure no browser tasks are accidentally quadratic in number of tabs or windows, etc.