So the ideal browser is a concept that is every day more and more elusive.
For my private use, I am using an older Mac with some memory consumption issues, so until I upgrade, I am using safari because it's the most lightweight, and while the extension support is the smallest of all, at least for very major things you are still covered.
For work, the Mac I am using is way more powerful, and yet I find strange issues. Vivaldi dies if I open more than 60-70 tabs at once but it doesn't even really matter, because all the Chromium based browsers that have said "don't worry, we will keep maintaining Manifest V2" feel like they are on a "danger zone" to me.
And then, I try to use Firefox and while the extension support is the most complete, many times I am finding unresponsive pages (usually tools like Google Meet, which I need to use because of work) or even worse: profile files get messed up and I start getting an error "There was an error, that's all we know" every time I try to log into any service using Google SSO.
So to summarize, at this rate I will have to migrate to Qutebrowser... or Lynx.
I have heard that the real underlying problem concerned resource usage (ten thousand regexp matches etc). But only now do I wonder why the browser's reaction is to remove an API instead of to limit the amount of CPU extensions can use.
So the ideal browser is a concept that is every day more and more elusive.
For my private use, I am using an older Mac with some memory consumption issues, so until I upgrade, I am using safari because it's the most lightweight, and while the extension support is the smallest of all, at least for very major things you are still covered.
For work, the Mac I am using is way more powerful, and yet I find strange issues. Vivaldi dies if I open more than 60-70 tabs at once but it doesn't even really matter, because all the Chromium based browsers that have said "don't worry, we will keep maintaining Manifest V2" feel like they are on a "danger zone" to me.
And then, I try to use Firefox and while the extension support is the most complete, many times I am finding unresponsive pages (usually tools like Google Meet, which I need to use because of work) or even worse: profile files get messed up and I start getting an error "There was an error, that's all we know" every time I try to log into any service using Google SSO.
So to summarize, at this rate I will have to migrate to Qutebrowser... or Lynx.
I have heard that the real underlying problem concerned resource usage (ten thousand regexp matches etc). But only now do I wonder why the browser's reaction is to remove an API instead of to limit the amount of CPU extensions can use.
The browsing experience is dramatically faster with uBlock. The thousands of regexps don't come close to the CPU or memory load of ads.
A 386 could handle a regexp fine. Compare that to audio or video decoding for ads. Not the same ballpark by orders of magnitude.
It's dead because Google makes money from ads. I shifted to Firefox ages ago.
That's good, at least more and more people will move away from Chrome.
In terms of HN probably. In terms of all users, probably very few