3 ms·
>I really don't care which browser is #1 in speed tests. You're in the minority then. The majority of users care, a lot, about speed, and Firefox is visibly sl
by andrepd 9y ago
>I really don't care which browser is #1 in speed tests.
You're in the minority then. The majority of users care, a lot, about speed, and Firefox is visibly slower than Chrome, probably one of the main reasons it has lost so much share.
Personally I care about both, that's why I am so conflicted about this update. But it's disingenuous to assume this is an unwarrented regression. You cannot get better in terms performance while keeping the extension system as it is. This reworking is necessary for Firefox to even compete wit Chrome. I understand the dillema but this is far from clear-cut one way or the other.
- roblabla 9y agoJust wanted to say that, annecdotally, I switched from chrome to firefox not because of speed, but stability, four years ago. Chrome would reliably crash on my laptop after opening three tabs, while firefox would let me open dozens without trouble. I guess it was an OOM issue, but I never really cared. Firefox worked, chrome didn't. The added extensibility, while nice, was mostly an afterthought. The only extension I'll miss is cliget, and hopefully it can be added back eventually.
- JohnBooty 9y agoThe majority of users care, a lot, about speed Yeah. I care about browser speed a lot; I'm one of those guys always looking for settings to tweak and measuring results and so forth. I spent I-don't-even-want-to-know-how-many hours a week using a browser so even small improvements become noticeable quality-of-life upgrades. But, still: 1. Benchmarks are important, but aren't always the best reflection of actual performance, either real or perceived. Subjectively, Safari on Mac and Edge on Windows "feel" fastest to me even though benchmarks say otherwise. Within reason, that's what typical end users care about: "feel" vs. benchmarks. (FWIW, Firefox is my main browser; I'm not telling anybody to use Safari or Edge) 1a. Chrome benchmarks the best, but it also uses the most memory due to its multiprocess model, so for users on memory-constrained devices (particularly with spinning HDDs, where swap's going to be really slow) I'm not convinced reality always lines up with benchmarks here 2. The user's network connection is still usually the biggest factor. 3. I don't think actual site content's getting much heavier. All this extra browser performance is just getting soaked the hell up by heavier and heavier ads. So I can't get as excited about browser performance as I used to.