bun VS zig

git clone https://github.com/Jarred-Sumner/bun.git

error: unzip is required to install Bun (see: https://github.com/Jarred-Sumner/bun#unzip-is-required

the first ops/s is also very much not covering a real example, you can't make sqlite faster then it is there is a limit on how fast you can make this. So first off both use the same C library below it (sqlite3) and that is doing the heavy lifting, then you go further and think about the JS part, where it even says in their source code https://github.com/Jarred-Sumner/bun/blob/e4fb84275715bb4de4b541f6de0ede4b5ce3e10a/src/bun.js/bindings/sqlite/sqlite.exports.js that it uses the same code as sqlite for transactions.

> This part, very early on in the Bun page, stood out. That’s a monetizable product, even if the code is open source.

bun isn't open source, it is source available at this point: https://github.com/Jarred-Sumner/bun/issues/241

It's "Zig" not "Zag". https://ziglang.org/ Zig is under heavy development, but there's a single page https://ziglang.org/documentation/0.12.0/ that is a reasonably comprehensive source of truth about the current state of the language.

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