I am confused.
- The "shipping Chrome alongside their application" part seems to refer to Electron; but Electron is hardly guilty of what is described in the article.
- The "learning web standards" bit seems to impune web developers; but how are they guilty of the Chrome monopoly? If anything, they are guilty of shipping react apps instead of learning web standards; but react apps work equally well (or poorly) in all major browsers.
- Finally, how is Chrome incompatible with web standards? It is one of the best implementer of them.
Shipping Electron junk, strengthens Google and Chrome market presence, and the reference to Web standards, why bother when it is whatever Chrome is capable of.
Web devs with worthy skills of forgotten times, would rather use regular processes alongside the default system browser.
Or actually learn how we use to ship software on the glory days of 8, 16 and 32 bit home platforms.
Now I do agree there are no alternatives for people that only care about shipping ChromeOS all over the place.
I don't even hate Electron that much. I'm working on a toy project using Electron right now for various reasons. This was just a bizarre angle to approach from.
Yes, Windows supported Electron-like applications back in the 90s with HTAs. If you want something modern and cross-platform, Tauri does this: