3 ms·
Alternatively using a WASM engine or maybe the kernels built in eBPF.
by elcritch 4y ago
Alternatively using a WASM engine or maybe the kernels built in eBPF.
- ilyt 4y agoThe overhead would make it not worth it, you'd be better off just running it in userspace. WASM started to become equivalent of "just rewrite it in Rust" here...
- liftm 4y agoWait, so I've been lied to? https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript https://www.destroyallsoftware.com/talks/the-birth-and-death...
- ilyt 4y agoLanguage doesn't need to be good to be popular for a long time. PHP was (is) previous "shit but lowest common denominator that everyone uses it" before JS took that mantle. Also "good" depends on the audience. Ability to cheaply hire a bunch of devs to whip up CRUD app is "good" quality of PHP/JS even if it might not make the language "good" from engineering perspective.
- liftm 4y agoIgnore the JS bashing (it is deserved but irrelevant here). I was referring to the part explaining the 2028-2040 METAL system where "we" gained 4% execution speed because we stuffed all things into a asm.js VM in kernel that can skip syscall overhead. But it's a joke video anyway.
- elcritch 4y agoI’d guess it’d be slightly faster. The WASM or eBPF would add some overhead, however you save on context switching costs from kernel to user land. So for IO heavy stuff like SMB it’d probably perform well.