this post was submitted on 14 Jul 2025
71 points (94.9% liked)
Programming
21593 readers
183 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I get all the advantages (portability and distribution mainly) but I also think we did the transition to web in the worst possible way. We basically took all the shitty solutions that were there 20 years ago and started improving them gradually at the same time as we moved everything to web. The result is that web apps are security and privacy nightmare.
What I think should have happened is that some standardized execution environment should have been defined that would use HTML/CSS for rendering but would also apply strict security. I would base it on web assembly, not javascript. You would be able to embedded this environment in a browser or install it at OS level. It would download an app package from a domain and by default only allow network communication with that domain. Everything else would have to be approved by the user. Basically something like web based android apps but stricter or Electron but lighter and distributed over the web. Instead of doing that we've spend 20 years perfecting lazy loading of JS scripts so that each website can have 400 trackers. And yes, I know we can do it now with Tauri but it's not very common.