> Fixing this is probably difficult to impossible.

It is absolutely possible to make a browser engine-based shell that is more efficient than Electron is. Electron has the wackiest setup imaginable, mashing together Node and Chromium, with two versions of V8 to boot.

That is what I am talking about. Who is making this happen!?

The issue is that electron is running a new chromium process for each application. This could be fixed easily sharing that process and making chromium more resource friendly.

And go back to the 80's where one app crashing can take down the whole system? No thanks. Apps would be able to overwrite each others memory then too, you'd get the full Amiga experience.

So make the singular processes run in a tighter sandbox where performance is necessary

Once you sandbox that much you've just reinvented processes.

Maybe something like Go + the system web view. Only question is what is "the system web view" in Linux.