I can't imagine many people would like to download a 60GB AAA game or something like Photoshop to run it in the browser.
I can't imagine many people would like to download a 60GB AAA game or something like Photoshop to run it in the browser.
Not saying we're there yet, but it's not hard to see where WASM could take us.
Difference being that WASM is kind of blessed format.
You won't get in the same universe as that until the web grows real threading support. Not this no-shared-data, ultra expensive, ultra heavy webworker nonsense.
Given SharedArrayBuffer seems to be un-shippable now due to Spectre, the planned future of WASM's threading seems uncertain. And without that WASM seems rather pointless to be honest. You just can't compete with native at anything compute when you can't use 80%+ of the CPU.
There are plenty of downsides to having ubiquitous WASM-compiled cross-platform "browser-native" apps, and having basically everything forcefully turned into an experience akin to ChromeOS out of convenience for app developers, but that doesn't feel like one.