[ocdtrekkie]

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.

[BuckRogers]

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.

[ocdtrekkie]

Of course, the sad state here is that a lot of apps are now Electron-based, so you end up with Chrome anyways. >.<

[BuckRogers]

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.