Disappointing, but not surprising. The performance of the browser is not an issue on my side. These are just synthetic benchmarks, so not very interesting to me. I wonder if one can “feel” (not just measure) the difference of performance when using both browsers. I don’t use Chrome and probably never will, so cannot compare.
Ok, FF got its ass kicked this time. It could be a good reminder to Mozilla that they should focus on their browser and its market share instead of continuing to pursue side quests that lead nowhere.
I will continue to use FF for reasons other than performance (good adblocker, etc), but it was a bit sad seeing that I could’ve been getting more out of my hardware by using another browser.
I just browse text based websites. To me the browser performance doesn’t really matter at all.
Does it support pwa? Does it allow to block ads and harmful content? That’s important to me.
Yeah, couldn’t care less if Chrome is faster when it is controlled by Google and actively working against extensions.
Not to mention we crossed a performance line maybe 10 years ago where browser engines on modern processors are basically trivial. Once we started having 8+ threads and the browsers got smart enough to leverage them, I’d bet bandwidth (or memory if you have many tabs), is a way more typical bottleneck.
