this post was submitted on 18 Sep 2025
59 points (100.0% liked)
Programming
24052 readers
528 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
These all sound like good improvements to WASM as a binary target, but... how do we STILL not have access to any kind of I/O? How is that not the #1 priority? No access to the DOM, no access to local storage, no access to networking... WASM will continue to be borderline useless until it can actually do the things an application needs to do, without having to implement some hackjob JS interop layer.
I/O and stuff like that is being done in the WASI proposals not in WASM proper. I believe most of this stuff is waiting for initial implementations at this point and then it becomes a proper standard.
I hate having to use js interop for simple stuff like manipulating the history stack or even just saving to the clipboard