WebAssembly proposal touted to improve Wasm web integration

"There are multiple reasons for this, but the core issue is that WebAssembly is a second-class language on the web. For all of the new language features, WebAssembly is still not integrated with the web platform as tightly as it should be."

"Oftentimes, JavaScript is simpler and good enough. This means [Wasm] users tend to be large companies with enough resources to justify the investment, which then limits the benefits of WebAssembly to only a small subset of the larger web community."

"Without the component model, he argued, WebAssembly is too complicated for web usage. He added that standard compilers do not produce WebAssembly that works on the web."

Mozilla and Google are collaborating on the WebAssembly Component Model to address WebAssembly's limited web adoption. Despite adding capabilities like shared memory, exception handling, and bulk memory instructions since 2017, WebAssembly suffers from loose integration with the web platform. This poor integration creates a suboptimal developer experience, causing developers to prefer JavaScript when possible. JavaScript's advantages in code loading and web API access make it a first-class web language, while WebAssembly remains complicated and inaccessible. Consequently, only large companies with sufficient resources adopt WebAssembly, restricting its benefits to a small portion of the web development community. Standard compilers do not produce WebAssembly compatible with web environments.

Read at InfoWorld