Wouldn’t this improve performance, startup speed, and reduce overhead from parsing multiple formats? Why hasn't anyone created a browser where the default language for sites is WASM?
Is it a technical limitation, security concern, or just lack of interest from the ecosystem?
I’d love to hear what the HN community thinks.
If this concept sounds interesting to you — even if you think it's flawed — I’d love to hear how you would improve or reshape it. Maybe there’s a better way to approach it, or a different angle I haven’t considered.
Feel free to break it down, challenge it, or build on it. That's exactly what I'm here for
Like how operating systems run .exe or ELF binaries — what if a browser did the same but with .wasm? Maybe not for regular documents, but for apps/games/tools where you want full control, performance, and custom UI rendering without relying on the traditional web stack.
Just brainstorming, I’m curious what others think.
If you want to know what WASM is actually a good fit for and what not, see https://queue.acm.org/detail.cfm?id=3746171
From memory, initial page load times are slower
and if you are passing your words through a llm before submitting them here, please stop, i'd rather see honest yet broken english
Here are some Avalonia WebAssembly demos:
- https://solitaire.xaml.live/
- https://bandysc.github.io/AvaloniaVisualBasic6/
- https://eremex.github.io/controls-demo/
Uno is a similar idea: https://platform.uno/
FerkiHN•7mo ago