3 ms·
I'm not too familiar with WebAssembly but I like the concept of compiling different source languages to a common "bytecode" language so it can run on various pl
by zorr 5y ago
I'm not too familiar with WebAssembly but I like the concept of compiling different source languages to a common "bytecode" language so it can run on various platforms.
However, with the way things are currently going, are we using WebAssembly to reinvent the concept of Java applets? It all sounds very familiar. And if this is the case, will it run into similar problems?
- kevingadd 5y agoIt's much lower level and has a robust sandboxing model, so the security issues with Java are not really a concern here. There are still security risks but they're different ones and generally less severe. Because it's lower level it's a more viable compile target for things that couldn't easily be compiled to Java, like C++ for example.
- matei_radu 5y ago(one of the authors of Spin here, and a WebAssembly enthusiast.) There are, of course, a lot of similarities between the Java or .NET runtimes and WebAssembly, and other comments made excellent points about the lower level nature of Wasm, or the isolation sandbox. I would also point out that there are significantly more languages that either have support for compiling to WebAssembly today, or that have started adding support (in the last month alone there were initial announcements for Python, Ruby, and .NET, for example).