2 ms·
By that argument, Python is "native" too then, with e.g. https://github.com/exaloop/codon https://github.com/exaloop/codon The reason why it doesn't quite work
by yencabulator 4y ago
By that argument, Python is "native" too then, with e.g. https://github.com/exaloop/codon https://github.com/exaloop/codon
The reason why it doesn't quite work out is that typically such a thing, AOT-compiled into native code, still carries with it its limitations and assumptions. It's technically native, but experiencing the native APIs only through a narrow peephole in
the fence.
If we let this meaning of "native" take over, we're gonna need another word for actually native things.
Sometimes, that works well enough, though!
- brundolf 4y agoThat's fair, although I guess "having a runtime" can also refer to things like running a garbage collector (which WASM doesn't but Python does, and even Go does), even if it's part of the same binary. But we're entering the territory where these terms start to get poorly-defined I think (new tech is pushing the boundaries!) Subjectively I think WASM's feature and non-feature list makes it plausibly kernel-friendly in a way that eg. Python isn't, but there may not be a concrete line to draw around that