On one hand, both ape and Wasmer rely on a “universal binary interface” to interact universally with the Operating System: Cosmopolitan (as a universal libc POSIX interface) in the case of ape, and WASI in the case of Wasmer.
This is great (I love WebAssembly). I just wish there was a way to run WebAssembly somewhat consistently between browser, linux/win/osx and Android. It seems like this fixes the browser and linux/win/osx part but no Android. Frameworks like emilk (i.e. egui with eframe) can do all three but packaging is rather complicated. This solves the packaging aspect with no solution to Android. Eh, maybe one day we will get there.
It would be cool to package Wasm for every platform easily. You could make a hermit runner for android that loads the module and wasi configuration from the hermit, but uses its own runtime instead of the one embedded in the hermit.
Excluding the Wasm runtime, the hermit's runner or hermit base is under 400 LOC:
https://github.com/dylibso/hermit/blob/1f6f51d0d6b3941c9616f... . Instead of reading the configuration and module from /zip you would use zip decoder on the hermit you want to run.
Wasmer already launched the exact same product one year ago (Aug 2022): https://wasmer.io/posts/wasm-as-universal-binary-format-part... (BTW, way more performant than the Hermit copy).
The only thing that Hermit does is using APE (Actually Portable Format), which we also analyzed on the second post of the series: https://wasmer.io/posts/wasm-as-universal-binary-format-part..., also published a year ago.