"duplication is becoming a significant performance drain" == Every electorn app bundles its own browser engine (as opposed to a single browser engine for the whole OS, like a shared library), which increases system RAM usage and hinders performance.
"They want to single-instance Electron with their own fork" == MS wants to support electron apps but they want to use a shared browser instance for performance.
They rightly believe that doing so with their own browser engine is a huge pain in the ass.
Might as well just use the real Chromium for all browser needs throughout the OS including electron apps instead of trying to reimplement it.
I can see that it increases disk space, but everything on top of that is questionable. I believe DLLs will share/reuse memory pages even if they were downloaded in separate bundles.
I have no idea if this correctly interprets the SwiftOnSecurity tweet, but that's the best I can make of it.
What, like https://en.wikipedia.org/wiki/Active_Desktop ?
A way to solve this is to make the JavaScript/html layer part of the OS, so that electron apps would ship as thin layers on top of a the system’s engine (The same way that java applications are thin layers on top of Java’s virtual machine).
Apparently, the way Edge is built doesn’t allow for replacing chromium in electron apps. So they need their own version of chromium instead.
I think it’s a better alternative to Apple's Marzipan.
It’s a tragedy for the Web but makes sense for Windows.
Anyway, as others have noted, this seems more and more prophetical every year:
https://www.destroyallsoftware.com/talks/the-birth-and-death...
https://twitter.com/garybernhardt/status/1069787375247622144
