Mozilla developer suggests the proposed WebAssembly Component Model will enhance web integration and elevate Wasm from a “secondary language” standing.
The WebAssembly Component Model, an architectural framework for creating interoperable WebAssembly libraries, applications, and environments, is being highlighted as a crucial development to move Wasm beyond its current designation as “a secondary language for the web.”
According to a February 26 blog post by Mozilla software engineer Ryan Hunt, the WebAssembly Component Model, which has been under development since 2021, would introduce vital capabilities for WebAssembly. These include:
- A standardized, self-contained executable package
- Compatibility across diverse languages and toolchains
- Management of WebAssembly code loading and linking
- Support for integrating with Web APIs
Hunt clarified that a WebAssembly component specifies a high-level API, which is then implemented using a collection of low-level Wasm code. He stated, “As it stands today, we believe that WebAssembly Components would be a positive step forward for the web.”
Mozilla is actively collaborating with the WebAssembly Community Group on the design of the WebAssembly Component Model, and Google is currently assessing the model, as noted by Hunt. In his post, Hunt contended that despite WebAssembly gaining features such as shared memory, exception handling, and bulk memory instructions since its debut in 2017, it has not achieved broader web adoption. Hunt attributed this to “multiple reasons, but the fundamental issue is that WebAssembly functions as a second-class language on the web.” He added, “Despite all the new language features, WebAssembly is still not as deeply integrated with the web platform as it should be.”
WebAssembly has been promoted as a binary format intended to enhance web application performance and has also served as a compilation target for other programming languages. However, Hunt argued that Wasm’s inadequate integration with the web results in a suboptimal developer experience, prompting developers to use it only when absolutely necessary.
“Frequently, JavaScript is simpler and sufficiently effective,” Hunt explained. He stated, “This implies that [Wasm] users are typically large organizations with enough resources to justify the investment, which consequently restricts the advantages of WebAssembly to a mere segment of the broader web community.” Hunt also pointed out that JavaScript offers advantages in code loading and utilizing web APIs, solidifying its position as a primary language on the web, unlike WebAssembly. Without the component model, he asserted, WebAssembly is overly complex for web usage, and standard compilers do not produce WebAssembly that functions effectively on the web.
