dwarf-2-sourcemap VS Cesium

> - A way way better tooling story.

I think this is a real paint point of WebAssembly but it's getting better. You can now compile C/C++ code to WASM using clang as it became a first class citizen in v8 (or later?). Of course, clang does not provide all the runtime goodies that emscripten does but if you limit yourself to use WASM for some part of your code that require performance then all you need to provide is a few Javascript glue code. For prototyping purposes I've bundle an npm package that bring clang to your frontend project without the need to install it through a package [0].

Chrome debugger now support WASM [1] but you still need to install an extension. I've started to work on a way to convert the DWARF symbols from the WASM binary into sourcemap on the fly [2][3] but it still rough around the edge and need some work but it can definitely be done. This would allow WASM debugging natively in any browser supporting sourcemaps.

You also have all the WASM binary tools that you would find for any other kind of executable format in WABT [4].

[0]: https://www.npmjs.com/package/@jdmichaud/wasm-toolkit

[1]: https://developer.chrome.com/blog/wasm-debugging-2020/

[2]: https://github.com/jdmichaud/dwarf-2-sourcemap

[3]: http://site.novidee.com/blog/blog-entry.html?article=2022082...

[4]: https://github.com/WebAssembly/wabt

Because Hacktoberfest is runing, I would like to share small project in which I'm participating. ForNeVeR/Cesium: C compiler for the CLI platform (github.com)

Technically you can always write you own C compiler like this project https://github.com/ForNeVeR/Cesium. Obviosuly C++ is much more complicated journey and require real investment. But at this point this is not CoreCLR limitations mostly.