Microsoft is working on this with their cross-OS Chromium based Edge - so far on Mac I see about a 60% reduction in RAM footprint using Edge. I believe the end goal is a single managed chromium runtime so each electron app wouldn’t need their own full Chromium instance.

>I believe the end goal is a single managed chromium runtime so each electron app wouldn’t need their own full Chromium instance.

I have spent hours searching the web for any clues as to Microsoft's intentions here. I would be grateful for any words on how you came to believe this.

Use to work in Windows and just from off the hand conversations with former colleagues.

Thanks for the reply.

He said "I believe", it's not an official statement from Microsoft, it's just his own opinion.

a7c32be153f91327db8a62932af28cac4dcfc7612a446c5021b9045a2af269b8

How will they manage different version requirements?

Isn’t that pushed into the app developers to maintain compatibility in other ecosystems?

My thoughts exactly... Now I have too many electron apps... So anything that helps to diminish my RAM consumption is welcome.

Good electron replacement should re-use your installed browser engine. That would reduce RAM consumption dramatically, while providing better security (because browsers usually update faster than individual apps).

You just created a “website”

There are a number of problems with locally-run websites.

One is that TLS is married to DNS, and no third-party CA would issue a certificate for localhost. TlS with self-signed certs generated on the spot becomes easy to forge.

Another is that no web browser suppoorts Unix domain sockets or a Windows equivalent as a an access protocol. You are stuck with IP-based access, wee above.

Third is that access to the OS is limited or forbidden inside the browser, for a good reason. Want to run a locally installed compiler from within your web IDE? Tough luck.

Electron solves all of these problems. It doesn't do it in the best way imaginable, but in some cases just a web site cannot be a replacement.

You mean, "website with native API's and (optionally) custom native chrome".

Developers don't use electron because it'll get its own browser engine instance.

Depends, there is a bunch of Electron apps that work just fine as websites (e.g. Slack, Spotify, Microsoft Teams, etc. As far as I know). I personally prefer running those in a browser tab to both save resources and benefit from privacy enhancing tools like content blockers, etc. I would be curious to know how many of the Electron apps actually need these extra native APIs.

Some of those you listed have extra features with electron. I was just being sarcastic with my remark. Like I don’t believe you can screen share with slack via a browser for example.

> Like I don’t believe you can screen share with slack via a browser for example.

If you can't, it's not the browser's fault. I can definitely screen share in Jitsi from the browser, so there's no technical reason Slack shouldn't be able to do the same thing.

You can show your screen but you cannot pass control.

Well, There is Apache Cordova. Cordova uses built-in webview. It also support windows and mac, but it's not as popular as electron because its api is not as rich as electron.

Electron supports native V8 extensions that are really fast. Cordova (at the time I tried it) only supported message passing which is very slow. Sufficient for many applications but for some it won't cut it.

Google had a project called Carlo to do this: https://github.com/GoogleChromeLabs/carlo But it's been discontinued now that the devs left the company.

I also see this project but you have to write Go to talk to the OS, not Node: https://github.com/zserge/lorca

Windows has had that feature since at least IE5. The main drawback was that "installed browser engine" might in practice mean "whatever ancient IE version this user who disabled windows update is using". Of course that is now mostly solved, and e.g. iOS offers the same feature.

But if you want broad cross-platform support "just get the locally installed browser engine" suddenly becomes a hard problem, unless this becomes a popular OS feature.

I think that the memory savings would be very limited, unfortunately.

This! A browser mode that removes all the browser UI but still uses the same engine would make web apps more practical as desktop replacements.

Back in the Win98 days, I think a .hta (html application) was meant to be that - like .html but opens as an "application". Never really took off though, I presume due to lack of APIs at the time.

It had access to the full VBScript or JScript runtime and WScript host. This means you could do OLE Automation, filesystem access, network access, registry access, and I believe invoke processes.

At the same time, companies were locking down WScript due to scripting viruses and HTAs that were impersonating other applications with their configrable icons.

This is, or was, sortof that: https://github.com/webview/webview/issues/305

Like Java?

There’s the “webview” project on github which does this.

Removing the electron apps works well. Usually they have a browser version, and that's still dogshit slow, but at least it shares more resources and has better sandboxing.