3 ms·

It's pretty amazing just how bad the tooling still is for Wasm given how much it's been pushed. (I'm a fan of wasm conceptually... I just can't handle all the E

• flohofwoe 4y ago
  Compared to similar compiler toolchains like the Android NDK or the MSVC command line tools, Emscripten really isn't that bad (for a C/C++ toolchain). Dramatically improving things would most likely mean becoming incompatible with mainstream C/C++ compiler toolchains (after all, the Emscripten compiler and linker needs to be pluggable into existing C/C++ build systems).
  • pjmlp 4y ago
    It isn't as bad as Symbian C++ used to be juggling MS-DOS batch files, Perl, make and Carbide/Metrowerks project files, but it could have less third party depedencies, between Python, node, Java, cmake and make. Ideally targeting WebAssembly from C and C++ compilers should be a -march switch, and Emscriptem would fade out.
    • flohofwoe 4y ago
      There's actually a super interesting project called wajic here: https://github.com/schellingb/wajic https://github.com/schellingb/wajic It's basically clang plus wasm-opt and some magic pixie dust which enables some of the most important features of Emscripten, but without the whole 'technology zoo' :)
      • pjmlp 4y ago
        Thanks for the tip.
• the_duke 4y ago
  The component model [1] with interface types will enable nicer tooling for things like linking and combining different languages, but it's been very slow moving and is still in flux. [1] https://github.com/WebAssembly/component-model https://github.com/WebAssembly/component-model
  • pjmlp 4y ago
    They keep reinventing what other polyglot bytecode environments already did, but they weren't part of a design by committee workflow.