3 ms·
Haha. Now the browser runs in the kernel. What can go wrong ? I think it was Microsoft that saw that running graphics in kernel is a bad idea. But, yeah, this
by hulitu 4y ago
Haha. Now the browser runs in the kernel. What can go wrong ?
I think it was Microsoft that saw that running graphics in kernel is a bad idea.
But, yeah, this was a very long time ago and why not make the same mistakes over and over again.
- brundolf 4y agoIt's not a browser (or even a piece of a browser), it's a method of statically sandboxing a native binary.
- yencabulator 4y agoWASM isn't really "native". A C/Rust/etc compiler can target it, but it's very much a non-native ISA, with its own "syscall equivalents", its own limitations, etc.
- brundolf 4y agoBut it doesn't have to be run in a runtime; it can compile directly to a platform-native binary. Internally it has limitations, as any sandboxed code would, but it lets you take native code and compile it to a native binary with sandboxing built-in
- yencabulator 4y agoBy 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
- chx 4y agoWhen I put webassembly into google the very first result has this to say: > WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Yes, browsers implement this nowadays but there are other implementations as well. You can compile them into llvm bytecode for example or there's another for the GraalVM etc
- jay-barronville 4y agoSorry but respectfully, you might want to research things before jumping to conclusions. WebAssembly doesn’t have anything to do with a web browser. It’s literally just a virtual machine standard. The standard was written with web browsers in mind (i.e., secure sandboxes within the browser environment), but nothing about WebAssembly’s semantics and runtime environment requires a web browser.