6 ms·
Curious why you chose Zig and not e.g. Rust.
by satvikpendem 3y ago
Curious why you chose Zig and not e.g. Rust.
- postalrat 3y agoI'm quite happy they did.
- satvikpendem 3y agoWhy is that?
- toughruck 3y ago[flagged]
- geodel 3y ago[flagged]
- satvikpendem 3y agoThere's Deno already if someone really wants their JS runtime in Rust. Personally, since everything just runs on a JIT JS runtime anyway, I don't really see to much of a difference between Node, Deno, and Bun, it's not like the JS is being AOT compiled via Zig or Rust, which would be very interesting, you could basically treat JS as a compiled language rather than an interpreted one, even if the JIT is already fast.
- kaba0 3y ago> it's not like the JS is being AOT compiled via Zig or Rust That would actually be slower than what you get from a JIT compiler.
- satvikpendem 3y agoI meant the compiler written in a lower level language that then binds to LLVM, as Rust is currently. Why would AOT be slower than JIT?
- zamalek 3y agoIn theory it could be: compiling for the specific latency profile and instruction-set of each individual machine. In practice that has never been done.
- kaba0 3y agoWhy would the implementation language matter for the compiler? It is a traditional input-output algorithm, it is either good and does many fancy optimizations for good output, or it isn’t. Sure, the speed of compilation may vary, but that’s a different question. Also, JS being such a dynamic language, it will likely perform better with a speculative JIT compiler, e.g. a shape can be assumed for a frequently used object. This is only possible with PGO to a degree.
- wredue 3y agoI suspect that this has something to do with it: https://zackoverflow.dev/writing/unsafe-rust-vs-zig/ https://zackoverflow.dev/writing/unsafe-rust-vs-zig/ Zig is also very easy to learn in comparison to rust.