Closed
Description
it's all about Python Stack inside a WASM (Web Assembly) container.
on WASM, there is two WebAssembly platform wasm/emscripten and a brewing standard in wassm/wasi :
- wasm/emscripten:
- supposes the WebAssembly is running surrounded per a [Javascript motor, and so must run inside a browser or node.js,
- pyodide is "designed" to run in this 'mature' state,
- pyscript seems to suppose the same for now.
- wasm/wasi:
- is for WebAssembly System Interface standalone application and runtime,
- is an non-finalised state of standardisation,
- is only a possible future option with of Python-3.11b2 at least,
- would require a target standalone runtimes like wasmtime or wasmer:
- wasmer is more targeted towards people who want to embed a wasm runtime inside an existing application that they're building,
- wasmtime is more meant to be used as a standalone program that runs WASI binaries directly.
- supposes the WebAssembly is running surrounded per a [Javascript motor, and so must run inside a browser or node.js,
"wasm/emscripten" is our object of experiment.
"wasm/wasi" is too pre-alpha, and out of pyodide scope.
Metadata
Metadata
Assignees
Labels
No labels