WebAssembly was supported by significant browsers in 2017 and released the MVP version. While the WebAssembly community is committed to making WebAssembly backward compatible, the WebAssembly application now in development can still be run in future browsers, but that doesn’t mean the WebAssembly functionality is complete, and MVP is by no means the final version. Instead, WebAssembly will add many new features that will fundamentally disrupt the work that WebAssembly can do.
To eliminate the misunderstanding of WebAssembly, the WebAssembly community group has a very detailed explanation of the future development path of WebAssembly in the form of a “skill tree” developed by characters in RPG games. They said that they have fully mastered the first of these skills and will need to unlock the entire skill tree slowly.
The community group said that the next goal of WebAssembly is to smoothly run those heavier applications, such as Photoshop, Gmail, and more. To ensure that such applications work well in the browser, they need to unlock a new batch of “skills”, including support for multithreading, SIMD (single instruction stream multiple streams), 64-bit addressing, streaming compilation (on download Compile the WebAssembly file at the same time), the layered compiler, the implicit HTTP cache, and a few other improvements.
For more features and specific progress, check out the original blog.