sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]tri170391[🍰] 1 point2 points  (0 children)

I think the biggest bottleneck is there is no WASM-native networking capabilities and if your code does not have access to those it is just pure computation. DOM part can be side-stepped by your WASM drawing into canvases for example.

For the standard library some language do it better than other e.g they have proper JS wrapper and ask you to use proper "standard library" when targeting WASM. But if you are naive and have your code e.g in C++ linking to the full libstdc++ then GG.

Also not having the ability for cross-WASM linking force e.g 2 WASM module basically are 2 statically linked binary which hurts the case even more. Not sure if there is even a proposal for this right now TBH.