Are WasmGC’s capabilities currently sufficient to meet the demands of mass production environments?

I asked Steiner about leveraging the WasmGC extension in industrial applications and he noted that “WasmGC is a (Part 5 of the series), with implementations in three browsers and the function transportation and delivery.” For Safari, he stated, the extension has also been integrated, but “we don’t know yet at what version of Safari it will finally ship.” Moreover, “support for WasmGC allows websites and apps like Google Sheets to use a progressive enhancement methodology: On browsers that support WasmGC, the new version is loaded, and on other browsers without support, the existing legacy version will suffice?”

While the efficiency benefits of languages like Java over JavaScript are a primary driver for WasmGC, it’s equally important to consider the diverse range of performance capabilities and garbage-collection approaches across various platforms. The prospect of seamlessly migrating tailored code to Wasm, allowing it to be deployed across platforms, including the browser, is now a tangible possibility.

The prospect of unleashing a plethora of languages beyond JavaScript on browsers is nothing short of astonishing, with far-reaching implications that could potentially trigger a seismic shift in the software industry. The possibility exists that relaxing JavaScript’s dominance over browsers could spark a creative resurgence among programming languages.