3 ms·
> They want to write targetted architecture-specific assembly, perhaps. Neither PNaCl nor the JVM gives you this.
by pcwalton 13y ago
> They want to write targetted architecture-specific assembly, perhaps.
Neither PNaCl nor the JVM gives you this.
- ajross 13y agoTrue enough, though NaCl does. I was mostly listing a bunch of stuff asm.js doesn't do to address the "intrinsically superior" comment, not giving a pros and cons list of specific technologies. Feel free to ignore that point if you like, I don't see that it meaningfully affects my argument.
- espadrine 13y ago> [emscripten] lags LLVM releases, it has glitchy behavior. Compare to clang and especially gcc which build robustly and cleanly everywhere and come with elaborate test suites. This isn't a toolchain I'm about to start betting a company on, for sure. Are you comparing emscripten to clang? Using clang alone won't get you something you can execute in a web browser — unless you include a CPU emulator in JS. If in fact you are comparing the asm.js workflow with the PNaCl workflow, they each rely on clang, sure, but PNaCl requires a bigger difference with clang-trunk. It is a plain fork. > PNaCl is essentially a modified version of Clang. This is done for two reasons. First, it eliminates an install-time dependency. Second, Clang was historically not supported on Windows (but this is beginning to change). Also, PNaCl has a unique, specific API (Pepper), which is very different from the way emscripten works. Finally, the comparative workflow to have your app work on the Web. PNaCl: write HTML/CSS/JS, write manifest, write PNaCl code, compile to pexe, rewrite the code to work with Emscripten, compile to JS via pepper.js. Emscripten: write HTML/CSS/JS, write native code to work with Emscripten, compile to JS.