_______ __ _______
| | |.---.-..----.| |--..-----..----. | | |.-----..--.--.--..-----.
| || _ || __|| < | -__|| _| | || -__|| | | ||__ --|
|___|___||___._||____||__|__||_____||__| |__|____||_____||________||_____|
on Gopher (inofficial)
HTML Visit Hacker News on the Web
COMMENT PAGE FOR:
HTML WebAssembly as a Python Extension Platform
mkoubaa wrote 8 hours 49 min ago:
The author never explains why they went for non-WASI runtime. Is there
an advantage to doing that?
pjjpo wrote 7 hours 50 min ago:
> For the use cases in this article, the best option is wasmtime-py.
They seem to have gone with a WASI runtime. Though to me, the caveats
after it, and throughout the article, make it seem like Wasm is more
difficult to deal with than PyO3's excellent ecosystem rather than
the opposite.
afiori wrote 8 hours 12 min ago:
An advantage of WASI is that it mostly works on non-WASI runtimes
too, as it can be compiled to one or more normal modules (with the
multi memory feature).
So a possible reason is that maybe they are not interested in
offering general interfaces but just a single python specific one.
In this case they could have likely used wasi for that too but I can
see how it could have been seen as an overhead
DIR <- back to front page