modules VS zig

Great experience with it. The examples in the repo, the issues and discussions sections, and the documentations are all very helpful. Alex and the other users are also quite hands-on in replying on each and every issue and discussion there.

We have some thin wrapper for uWebSockets.js that lets us do the following:

- parse request json

- parse request multipart data

- serve response json

- serve response buffers

- serve response streams

- serve response static files

- support async handler

- support multiple async handlers (middlewares)

links are here

- https://github.com/joshxyzhimself/modules/blob/main/uwu.mjs

- https://github.com/joshxyzhimself/modules/blob/main/uwu.d.ts

- https://github.com/joshxyzhimself/modules/blob/main/uwu.test...

internally we just serve http, then it goes through caddy or haproxy depending on the project's needs such as tls, caching, etc.

there are other similar projects too that tries to deliver express-like api:

- https://github.com/kartikk221/hyper-express

- https://github.com/nanoexpress/nanoexpress (defunct)

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