itk-wasm VS emsdk

This is an example to demonstrate browser-based debugging of C++-generated WebAssembly. For more information, please see the target="_blank" href="https://wasm.itk.org/examples/debugging.html">associated documentation.

Effective debugging results in effective programming; itk-wasm makes effective debugging of WebAssembly possible. In this tutorial, adapted from the itk-wasm documentation, we walk through how to debug a C++ data processing pipeline with the mature, native binary debugging tools that are comfortable for developers. This is a fully featured way to ensure the base correctness of a processing pipeline. Next, we will walk through an interactive debugging experience for WASI WebAssembly. With itk-wasm, we can debug the same source code in either context with an interactive debugger. We also have a convenvient way to pass data from our local filesystem into a WebAssembly (Wasm) processing pipeline.

In this post, adapted from itk-wasm's documentation, we provide a C++ Wasm processing pipeline tutorial that demonstrates how we can write elegant processing pipelines in C++ via itk-wasm's CLI11 command line parser, which provides a rich feature set with a simple and intuitive interface. At the end of this tutorial, you will have built and executed C++ code to Wasm for standalone execution on the command line and in the browser.

While we recommend following along step-by-step, the complete example can also be found in the examples/ directory of the project repository.

One place that I’ve found some real, open source unit tests to look at for an example is in the emsdk for emscripten: https://emscripten.org

Your default path was set by emsdk, given where the path is pointing. Your modified path is the path the installer linked in the Godot docs sets, just typically that kind of stuff doesn't override existing variables. This is a good thing to keep in mind in general as if you end up having to use a different version for something else in the future and just install it expecting the installer to update it for you, you will likely run into the same issue.

Emscipten C/C++ to WebAssembly compiler.

I am playing around with Emscipten which wraps around clang to compile C/C++ code in WASM binary and provide some glue-code API to embed WASM binary into JavaScript. Look into MDN Docs and Emscripten SDK to get started.

Elm is a different approach that compiles into JavaScript. In the extreme case, you have Emscripten which will compile many language into JavaScript but will feel really clumsy compared to using JavaScript in a lot of cases.

https://emscripten.org/ ?

SQLite is a pretty popular database and it's a critical dependency for many different applications. By compiling it to Wasm32-wasi, you can add it to any WebAssembly module.

This enables a new set of possibilities for Wasm and SQLite. For example, now you can run a full WordPress application in the browser [1][2] / server [3] using the same Wasm module. Note that for the browser these projects use Emscripten [4], but in the future the same Wasm32-wasi module will work.

In general, any environment that includes a wasm runtime can potentially run applications that uses SQLite under the hood. Before, it wasn't possible.

- [1] https://wordpress.wasmlabs.dev/

- [2] https://developer.wordpress.org/playground/demo/

- [3] https://wasmlabs.dev/articles/running-wordpress-with-mod-was...

- [4] https://emscripten.org/

The emscripten interface for the assimp library. It runs entirely in the browser, and allows you to import 40+ 3D file formats and access the result in JSON or glTF format. This is not a full port of assimp, but an easy to use interface to access it's functionality.

Three.js is written in JS and loads like a JS library on a modern website. Godot is a binary application transpiled to WASM (with the help of emscripten), resulting in a pretty large initial payload. Godot provides JS integration, but it feels less "native" with its layers of abstraction.