just VS zig

just

https://github.com/just-js/just Is another for a V8 runtime, it really shows how well optimized it is. https://www.techempower.com/benchmarks/#section=data-r21

i just tried recompiling v0.0.2 (https://github.com/just-js/just/releases/tag/0.0.2) of just-js and comparing it to current. for the completely static build on ubuntu 22.04 i see following:

0.0.2 (v8 v8.4.371.18) - file size: 15.2 MB, startup RSS: 8.4 MB

Not at all. Javascript, as well as java compiled into the bytecode, but just incrementally and at the runtime. You cannot compile typescript into bytecode directly (at least it intend to be like that). You can even compile js to executable (https://github.com/just-js/just). So no, typescript transpiles to javascript, whereas scala compiles to bytecode, it's different things

Trust me, these guys are insane and go to really extreme levels and use optimization techniques which are not generally prevalent among the general programming fraternity. for eg, look at pico.v it is awesome and just-js is truly unbelievable, then there is faf, most of them combine low level programming trickery to reach those insane numbers. Also some of the code may not be useful in a production app but they actually extract the juice out of the metal at every instance. Memory optimizations, compiler optimizations, postgresql wire implmentations, rust black magic, these guys are really crazy and passionate.

There is an issue proposing this approach: https://github.com/ziglang/zig/issues/4284

https://github.com/ziglang/zig/issues/224

e.g.:

> > When debugging/prototyping, it's useful to comment out a line without having to refactor, e.g.

When writing code in a scripting language, sometimes you need that extra bit of performance (or maybe an async feature from Zig).

NodeJS is by no means a slow runtime, it wouldn’t be so popular if it was. But compared to Bun, it’s slow. Bun was built from the ground up with speed in mind, using both JavascriptCore and Zig. The Bun team spent an enormous amount of time and energy trying to make Bun fast, including lots of profiling, benchmarking, and optimizations.

ntdll.dll!RtlUserThreadStart()

There are valid reasons to use APIs from NTDLL. Where I disagree with zig#1840 is the idea that it is always better to use NTDLL versions of API. Every other software ecosystem uses the standard Win32 APIs and diverging from that without a good reason seems like a good way to have unexpected behavior. One concrete example is most users and programmers expect Windows to redirect some file system paths when running on WOW64. But this is implemented in Kernel32, not ntdll.

https://github.com/ziglang/zig/issues/11894

Zig also has an IRC channel on libera (#zig) that is moderated by Andrew Kelley.[1]

[1] https://github.com/ziglang/zig/wiki/Community