I suppose this is in the same realm as what some people are trying to do with WASM, creating a common execution environment? This is built on RISC-V instead though. I wish I knew more about the limitations/capabilities of each approach, but in any case a future where applications are built for a common VM seems like something we've been building to for a while, the modern web being the closest we've come.

▲

apitman 2 days ago | parent | next [-]

I did a brief comparison a while back, specifically WASM vs libriscv for. I decided to go with WASM, primarily because it was much more closely designed for this sort of thing, and it works in browsers. libriscv is really cool and impressive though.

EDIT: Found this link in my notes as well: https://news.ycombinator.com/item?id=24900376

	▲	trj 2 days ago \| parent [-]
		libriscv looks amazing but its's much larger. It says "Less than 40kB total memory usage". My first version (unpublished) of uvm32 was called uvm80 and emulated a Zilog Z80 CPU. My aim is to have a safe, embeddable sandbox for any device, rather than the best performance.

▲

a day ago | parent | prev | next [-]

[deleted]

▲

IshKebab 2 days ago | parent | prev [-]

See https://opensource.googleblog.com/2025/11/secure-by-design-f...

This looks like it has a smaller code footprint at least. I'm not sure RISC-V is a very good target for this sort of thing. E.g. decoding the immediates in software is going to be very slow, whereas in hardware it's fast.

But on the other hand it is a stable target and can be configured to be a lot simpler than WASM.

	▲	trj 2 days ago \| parent [-]
		Thanks for the link, Wasefire looks interesting. I suspect that their design goals are very different to mine. https://github.com/ringtailsoftware/uvm32?tab=readme-ov-file...