wasmi VS duckscript

There are lots of solutions to this, I was randomly looking into this yesterday purely out of curiosity and it looks to me like wasmi is the current go-to option.

Hello guys, i was looking for a no std wasm interpreter and i found out about wasmi: https://github.com/paritytech/wasmi/, but when i tried it i get an error module env not found. I suspect that in my program i call an extern function putchar() to be able to print and wasmi doesnt support that, but other interpreters i tried support it, for example wain. Are there any alrernatives, or am i doing sth wrong here. I dont have a deep wasm knowledge, i was just wanted to experiment with wasm in a no std enviroment. Heres my code:

Currently i'm using it in cargo-make but will also use it later to parse args for duckscript commands.

At it's most basic you could make a really simple interpreter by just doing such a thing, and there is essentially already such a simple language like that built for/in rust called Duckscript (rust has a surprisingly large number of little embedded languages), and that would be completely and entirely sufficient for many purposes, though if you want speed then you'll need to JIT or AOT the code, which is why wasm is so handy as you can interpret or JIT (or even AOT it with wasmer) without the much larger overhead of a, for example, javascript or java embedded runtime.