logoalt Hacker News

bfleschtoday at 5:00 PM2 repliesview on HN

Looks good, nice features. But somehow the spark does not ignite on my side because it feels too artificial. I don't know if the metrics are faked, if the convenience functions actually work, if there is any proper hardening.

I can accept if stuff is vibe coded and has autogenerated README. But even the announcement blogpost is AI-generated, and I personally have zero data points to see if your understanding of software quality is the same as mine.

It's a weird world, if this would've been announced without any AI disclaimers some years earlier I would've eaten it up without a doubt. But right now if I see a fancy README with several good-looking command line parameters I immediately wonder if the README is hallucinated and the command line parameters actually exist.


Replies

losfairtoday at 5:29 PM

Hi, author here - a few critical pieces of this, like async-ebpf, were written long before those coding agents were released. I use AI assistance a lot when creating zeroserve itself, but I manually check AI output and take responsibility for it :)

show 2 replies
gigatexaltoday at 5:04 PM

Given the benchmarks:

Small static file (174 B) - the bread and butter of static sites:

server req/s p99

zeroserve 36,681 5.4 ms

nginx 31,226 7.8 ms

Caddy 12,830 22 ms

zeroserve serves small files about 17% faster than nginx on a single core, with a tighter tail. HTML pages, small JSON, CSS - this is the case zeroserve is tuned for.

Large static file (100 KB):

server req/s throughput p99

zeroserve 8,000 782 MB/s 22 ms

nginx 7,600 773 MB/s 28 ms

Caddy 6,084 590 MB/s 44 ms

I'd go with a more storied project that's been audited, battle tested, hardened etc than this upstart. There's not enough improvement to justify the risk.

show 1 reply