I'm confused by it, too. The main reason I've preferred Firefox to Chrome for years has been performance. It's pretty much the same in responsiveness and uses far less memory.
Chrome being the fastest browser is ancient history.
Chrome being the fastest browser is ancient history.
Bloated websites (usually Google ones) would actually lock up the entire Firefox UI, and Windows would recognize the browser application as "Not responding" until the page finished loading. In the case of a super bloated site like the old Google+, that could be as much as twelve seconds non-responsive while all the cruft loaded up.
I am back on Firefox release channel now, and pretty satisfied with current performance, but looking forward to Quantum.
The whole issue of sites freezing and lagging without using Chrome is concerning, and it's not pushing me to use Chrome. I think that's Google's aim by creating that situation but I'm not budging.
It's pushing me to more native apps in both the iOS AppStore and Microsoft Store.
It's probably inevitable that shoving Node based apps into the market falls flat in favor of more efficient native code solutions due to mobile. I've been viewing Electron as a temporary stopgap with that in mind at least.
57, once it got closer to Beta, was the first version I could develop with.