The web-as-vm has nothing wrong, but it has eaten the web-as-interactive-documents. And now to have a lightweight web experience not focused on webapps i am stuck with the heavyweight runtimes with even more stuff on top just to disable features, lock down invasive websites that grabbed the newly available features to implement invasive anti-features, etc.
[1] https://learn.microsoft.com/en-us/windows/win32/controls/lis...
[2] https://www.geoffchappell.com/studies/windows/shell/comctl32...
These are non-trivial things.
Now that I’m thinking about it, I still don’t have convenient sandboxing of desktop apps.
BTW you can have easy app sandboxing today using flatpak, works like a charm on Fedora.
Allegedly [1] a lot of popular packages use "--filesystem=host", which completely defeats the security of sandbox by granting access to the user's home directory (i.e, allows arbitrary code execution through modification of configuration files).
I think I would rather trust the browser's sandbox, where sandboxing has been in place from the start and applications are designed for it.
Ultimately it comes down to who you trust the most. Do you trust your cloud provider to not look at your data and sell you off or do you prefer trusting your local application to not fuck around where it shouldn't?
20 times more complex - this comes with doing more. 15 years ago there was no CI/CD.
Write CSS - don’t have to given Sass, components, and bootstrap.
Performance is worse - look at v8 benchmarks, look at webgl and Wasm. The browser itself can run much faster today, and people are doing more with it.
JS barebones - just one package. https://github.com/stdlib-js/stdlib. - and the node ecosystem is a feature not a bug.
Look elsewhere - every other UI framework we’ve tried before has been worse in terms of compatibility, functionality, flexibility, and available prebuilt tooling.