Hacker News new | ask | show | jobs
by asdgkknio 3143 days ago
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.
2 comments
ocdtrekkie 3143 days ago
The main reason I originally left Firefox (for Edge, mind you, I don't touch Google software anymore) was the single-process issues they fixed with electrolysis which came out in Firefox 48.

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.

link
BuckRogers 3143 days ago
I'm a Firefox or native-platform browser guy. Some sites are laggy on anything except Chrome. Browsing around Groupon causes periodic freezes for me in Firefox. I haven't noticed this particular case in Edge but it does lag over time on other sites.

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.

link
ocdtrekkie 3143 days ago
Of course, the sad state here is that a lot of apps are now Electron-based, so you end up with Chrome anyways. >.<
link
BuckRogers 3143 days ago
I've been wondering about that, and how for the "app" side of the webstack if wasm will wipe out the traditional webstack "apps" and put things back in a more orderly fashion. Webstack for web documents, wasm for applications. If wasm becomes the univeral app platform for many appstores and the browser, I'd welcome that over Electron.

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.

link
oatmealsnap 3143 days ago
I had major problems using LiveReload and BrowserSync during development (two tools that automatically refresh a local website when you make changes to your code). After a few saves, it was too slow to use. Chrome and Safari would refresh about twice as quickly, and remain fast.

57, once it got closer to Beta, was the first version I could develop with.

link