So, What WebAssembly stands for?
Why WebAssembly is needed?
Imagine a world where you can build software with C++, Rust, Python, Go, or even COBOL the deliver that software to the end-user in a Web browser without any installation and near-native performance, that world became a reality in December 2019 when web assembly became an official W3C standard.
Web development is itself a challenging part where things are rapidly evolving and WebAssembly will be a new addition. With this, we may see the web used in a lot of new applications which is not possible in today’s scenario. WebAssembly will open more doors by freeing up from the shackles of today’s web.
- Write performance-critical code using other languages like c/c++.
- It loads significantly faster on mobile devices.
- Sharing of code between applications.
WebAssembly is still in its infancy. Only time could tell us how it will evolve. For some time being wasm and asm.js will stay equivalent to support polyfilling of wasm via JS. After that wasm and JS may diverge. To bring a new standard into the web will be as tough as exciting it sounds. But the upside is that we now have an open, vendor-neutral, cross-browser, experience-based standard, commitment, and involvement to major open-source implementation on the web.
My blog post