> and how to use that information to come to a compromise
Electron is popular because it uses regular web tech to build apps. Electron is slow because it uses regular web tech to build apps.
Where is the compromise?
Another question is "popular with who"..
> the developer experience, the development speed, the ability to share code across runtimes
I don't know what you mean by "the developer experience", but surely any high-level language gets you speedy development, and architectural agnosticism?
A compromise would be to use Electron/Chromium as shared libraries so the bulk of those apps would be using the same 500 MB - nearly free lunch for users who would have Chromium running all day either way.
Electron is popular because it uses regular web tech to build apps. Electron is slow because it uses regular web tech to build apps.
Where is the compromise?
Another question is "popular with who"..
> the developer experience, the development speed, the ability to share code across runtimes
I don't know what you mean by "the developer experience", but surely any high-level language gets you speedy development, and architectural agnosticism?