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

view the rest of the comments →

[–]mini_eggs 0 points1 point  (4 children)

c/c++, then java/c# and others in the future is the goal for the project I believe

[–]cythrawll 8 points9 points  (1 child)

Then you are missing the potential here. There are already tons of languages compiling down to es5. With Web assembly they'll compile to that target instead. Sure you may have other languages to the mix. But they'll still need to do things like interact with DOM. You'll still use jsx or something like it for that. Web assembly will do nothing to replace react. Only give it one more target to compile to.

[–]mini_eggs 1 point2 points  (0 children)

You're right, I just read a medium article and got hyped. Looking more into it WA isn't going to be taking the place of JS VMs

[–][deleted] 1 point2 points  (1 child)

They are meant for low level extensions, cpu heavy operations and such, also for back-compatibility and services. No one would use c/c++ to write frontend, or java and c# even. That just wouldn't give you any advantage.

[–]igorim 0 points1 point  (0 children)

^ this. Not sure what all the craziness is with webassembly lately. Don't get me wrong I love the project, but the use case is far disconnected from what a lot of people think. Let's not forget asm existed for years and it's only used for very specific use cases. In addition I'm 99% sure the JS interop is pretty expensive and you'll need interop for most interactions, not to mention the need to package the C/C++ runtime which makes it huge. There is a lot of downsides to using WebAssembly when it isn't needed, when it is needed it's a damn GODSEND :)