I have this dream of a single WASM runtime environment across web, desktop, mobile with devs writing apps once, compiling them down to WASM, distributing them over the Internet, and users running them on any platform they like.
You write the app once and it can be compiled to WebAssembly that works across web, desktop, and mobile.
In reality to take full advantage of Blazor you’re probably going to use Blazor Server/hybrid for desktop and mobile but the principle is the same, you’ve only written your app once but it works in every environment.
That only works with c# though. What they are suggesting is compiling any arbitrary language to wasm and run that anywhere. Which is technically already possible with WASI and any of its supported runtime.
I think you just described Blazor WebAssembly
Blazor and webassembly are different things. Webassembly is a runtime, blazor is a framework built for webassembly. They do not compare
Blazor WebAssembly ticks the boxes that @treechicken@lemmy.world described.
You write the app once and it can be compiled to WebAssembly that works across web, desktop, and mobile.
In reality to take full advantage of Blazor you’re probably going to use Blazor Server/hybrid for desktop and mobile but the principle is the same, you’ve only written your app once but it works in every environment.
That only works with c# though. What they are suggesting is compiling any arbitrary language to wasm and run that anywhere. Which is technically already possible with WASI and any of its supported runtime.