2 ms·
You don't need wasm for that, anything that just throws up a huge <canvas> in the browser will do. What I expect wasm to do is to introduce new frameworks that
by jeroenhd 4y ago
You don't need wasm for that, anything that just throws up a huge <canvas> in the browser will do.
What I expect wasm to do is to introduce new frameworks that take whatever the devs consider to be native behaviour and plonk it right into the browser. There are already plenty of demos out there that break the most basic browser features because compiling all of Qt into a canvas view can't possibly render a native experience.
Then again, we've lost the concept of "native" years ago when we started packaging browser engines with popular applications.
Soon we'll reach a stage where native code gets compiled to wasm, bundled with a slightly outdated copy of Chrome and sold off as a "native application".