Look, Electron is a disaster. It's a lazy, bummed-out way of blasting sparrows with tactical nukes.
I'm not sure I even understand the reasoning behind the thing. Yeah, fine, we want to do the web-thing in a desktop applikation. But then why a whole Chrome with a showroom of kitchen sinks? We can still run an html-stack without gobbling up every ressource in sight, you know.
I'm looking at this HN page in latest Firefox (and assuming Chrome would be much the same). And in another window the same page in Netsurf (http://www.netsurf-browser.org). One needs half a gigabyte and then some. The other does fine in 50MB.
Plenty of stuff which gets wrapped in Electron actually works without a hitch in Netsurf and similar minimalistic environments.
How would you implement a GUI app in Netsurf that according to their release plan has no support in the rendering engine for JavaScript dynamically changing the DOM? Not to mention the JS support being incomplete anyway even though they are only supporting old standards ("most of HTML 4 and CSS 2").
I'm not sure I even understand the reasoning behind the thing. Yeah, fine, we want to do the web-thing in a desktop applikation. But then why a whole Chrome with a showroom of kitchen sinks? We can still run an html-stack without gobbling up every ressource in sight, you know.
I'm looking at this HN page in latest Firefox (and assuming Chrome would be much the same). And in another window the same page in Netsurf (http://www.netsurf-browser.org). One needs half a gigabyte and then some. The other does fine in 50MB.
Plenty of stuff which gets wrapped in Electron actually works without a hitch in Netsurf and similar minimalistic environments.
Professional pride, anyone?