In a blog post discussing web browser evolution and current limitations, Joey suggests an alternative approach called WASM Wayland Web (WWW). He argues that with only two major engines dominating the market and making new entrances challenging due to complex standards, it’s time for change. Instead of relying on HTML, JavaScript, CSS et al., why not create a browser solely focused on running Web Assembly (WASM) blobs?
This WWW concept would provide tabs, URLs but no traditional web rendering elements like HTML or CSS. It would operate by simply fetching HTTP packets of WASM files instead of conventional web pages. Joey believes this shift could lead to more openness in the browser ecosystem as it simplifies development and reduces vendor control over standards.
With such a system, users can easily build custom browsers tailored for specific needs like RSS support or IPFS integration without facing massive maintenance challenges. Additionally, adding extensions would be simpler since they interact with WASI (Web Assembly System Interface) components rather than deeply integrating into the browser core itself.
Although concerns about potential proprietary software arise due to corporate websites’ current “source” situation, Joey emphasizes that this approach could ultimately democratize web browsing by enabling diverse innovation sources beyond existing giants. Moreover, users still have freedom to use HTML if desired through incorporating a suitable WASI component model.
In conclusion, Joey envisions dual innovation paths emerging from his proposed WWW concept – one staying within the current browser landscape with all its complexities and limitations; another breaking free into uncharted territory where Web Assembly takes center stage. He acknowledges this isn’t his project to build but hopes someone else will take up the challenge for a more competitive web browsing future.
Complete Article after the Jump: Here!