Offer a high level programmable interface?

[yvan-sraka]

I know we choose to use https://github.com/adrien-zinger/wasmer-as to read strings in the context of running SC written in https://www.assemblyscript.org/

But it is worth also offering a high-level programmable interface based on https://wasi.dev/ as I experimented here https://github.com/massalabs/sc-runtime/tree/wasi-env to let people try (at their own risks) to embark small interpreter like https://bellard.org/quickjs/ on SC runtime provided, even if it will be slower and hackier.

My question could be also reformulated as:

• we could offer an easy-to-use and fast solution that constraint 90% of our beginner users to use AssemblyScript
• do we offer a solution more "language-agnostic" slower (maybe that could cost more gas) solution for 10% of our advanced users (stats are wrongly approximated) than could produce by themselves a wasm binary targetting WASI and let the choice to users to use Rust or a bundled interpreter or whatever custom solution they want?