because phones, computers, and browsers are only getting better.
If your software is inefficient, throwing more hardware at it will only help up to a certain point.
However, the one big thing missing from WebAssembly (yet?) is native support for DOM manipulations. As long as it's not there, WebAssembly is out for most people.
👨🏫 Co-Founder of This is Learning, Organizer of AarhusJS
✍️ Writer, Speaker, FOSS Maintainer 📗 Author
🏆 Microsoft MVP 🌟 GitHub Star
🌊 Nx Champion 🦸 Angular Hero of Education
If your software is inefficient, throwing more hardware at it will only help up to a certain point.
However, the one big thing missing from WebAssembly (yet?) is native support for DOM manipulations. As long as it's not there, WebAssembly is out for most people.
For now we rely on JavaScript-based companion libraries to make DOM manipulations. I imagine this is how Blazor does it.
Check this
But yes, thank you!