wasm-micro-runtime VS raylib

Finally, I landed on Bytecode Alliance's WebAssembly Micro Runtime (WAMR) wamrc compiler.

The person I replied to just said it is 266MB because it includes a compiler, and that obviously isn't true.

https://github.com/bytecodealliance/wasm-micro-runtime

This says 4000 lines

https://github.com/explodingcamera/tinywasm

What are we talking about here? There is obviously no reason a wasm jit has to be 266 MB

To be able to embed WASM-compiled languages for embedding you first need a small WASM runtime you can depend on (and things like ref types, GC etc which have been standardized only in the last couple of years).

That didn't exist until recently, but now you can use https://github.com/bytecodealliance/wasm-micro-runtime/blob/...

I am not aware of anyone using this yet, but I hope to see that become common in the next few years.

What would be the recommendation to run on ESP32?

https://github.com/wasm3/wasm3? https://github.com/espressif/esp-wasmachine ? https://github.com/bytecodealliance/wasm-micro-runtime/tree/... ? https://github.com/TOPLLab/WARDuino ?

Interesting artifact of time it would be. Harfbuzz uses https://github.com/bytecodealliance/wasm-micro-runtime to execute wasm, so when compiled it would be wasm runtime running under another wasm runtime.

We added Cosmo platform support to WAMR[0], to enable our Hermit[1] compiler and runtime.

[0]: https://github.com/bytecodealliance/wasm-micro-runtime/tree/...

[1]: https://github.com/dylibso/hermit

Here is what you are looking for: https://github.com/bytecodealliance/wasm-micro-runtime

No longer does Wasm/WASI need JS host! There are many spec-compliant runtimes built for environments from tiny embedded systems up to beefy arm/x86 racks:

- https://github.com/bytecodealliance/wasm-micro-runtime

- https://github.com/bytecodealliance/wasmtime

- https://github.com/wasmerio/wasmer

- https://github.com/tetratelabs/wazero

- https://github.com/extism/extism (disclaimer, my company's project - makes wasm easily embeddable into 16+ programming languages!)

The WASM core 1.1 infrastructure is already available in a very strict defined more or less guarantied compatible form on nearly any final target. Even on very small devices for embedded computing (WAMR takes less then 85kB and supports even trusted computing etc.) and in contexts, where usually no other low level development tools are available (for example within the context of Webbrowsers, sandboxed execution etc.)

I don’t have a review, but here’s a significant project using it in a complicated cross platform build with different systems dependencies: https://github.com/raysan5/raylib/blob/master/build.zig

They also have a cmakelists.txt to compare against.

One of the nicer things is that if you’re working with less technical folks, they only need to download the zig binary because it bundles the entire toolchain.

As I play around with raylib, the small, easy, and exceptionally cool game library, I met a small issue. There is no elegant way of packing files together. When I use a texture or audio, or any external resources, I either need to convert it into a C++ header that declares a byte array filled with that resource, or making sure the the user having the resource at the particular place. The first approach is no good when comes to loading new resource after compilation, while the latter approach is kind of awkward and too easy to break.

For this most recent assignment we were tasked with contributing a larger feature to an open source project. During my time with the previous assignment I worked on a game engine called Litecanvas, inspired engine by libraries like raylib and p5.js/Processing.

Let's take a look at another API. Raylib. Now Raylib does a little bit more than just load images. Raylib is more of a game framework than a single-purpose library. It will create a window, handle input, load images, render pixels, handle loading and rendering fonts, and so on. Even though Raylib does multiple things, it doesn't go overboard. It tries to be simple yet robust. There's a clear vision for the library. They didn't try to force a GUI editor into the API or an alternative string type. It had one goal and that is to become a game framework. What happens when Raylib has added all the features it needs to add? Well, call it feature-complete and just move on. There's no need to bloat an API for no reason other than you "felt like it".

Don't like having to use gigantic game engines to make games? Here's a whole suite of beautifully simple libraries with bindings for a lot of languages: raylib

Do like playing video games? I know I do; in fact, I enjoy it so much that I learned how to make video games. So, for a recent course I’m taking in school for open-source development I decided to focus on Raylib. Raylib describes itself as “a simple and easy-to-use library to enjoy videogames programming.” Written in pure c with bindings for almost any other programming language such as c++, Rust, and Python. It is a flexible tool which can work in almost any environment.