Except for Game engines, WebAssembly is pretty much pointless, given the peer W3C standards.
For any high-performance computation, you already have a WebSocket standard that can be used for offloading the computation to high-end servers.
For Visuals, Sound and GPU you have WebGL, WebAudio and WebGPU standards (the last one is upcoming).
For Edge computing, you have WebWorkers (if the device has browser) or other (more better) options in the form of Embedded languages (ERLANG, C etc.)
And then, even for game programming, no AAA-rated game targets WebAssembly. So, unless you are an indie who is using some OSS like Unity for game development, WebAssembly is pretty much useless in business environments.
Not to mention the architectural anti-patterns of mixing the business layer with the presentation layer, which goes back to the same problems of WCF and Java on Web.
To summarize, its pretty much hard to find a genuine real-world business use-case for WebAssembly. It is better to stick to other W3C standards.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Except for Game engines, WebAssembly is pretty much pointless, given the peer W3C standards.
And then, even for game programming, no AAA-rated game targets WebAssembly. So, unless you are an indie who is using some OSS like Unity for game development, WebAssembly is pretty much useless in business environments.
Not to mention the architectural anti-patterns of mixing the business layer with the presentation layer, which goes back to the same problems of WCF and Java on Web.
To summarize, its pretty much hard to find a genuine real-world business use-case for WebAssembly. It is better to stick to other W3C standards.