You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I know we choose to use https:/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:/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:
wasm
binary targettingWASI
and let the choice to users to use Rust or a bundled interpreter or whatever custom solution they want?Beta Was this translation helpful? Give feedback.
All reactions