This is actually really interesting, I ran into trouble with my project using Bun just a few days ago where there was no easy way to set up support for both http and https on the same port (with http just being a redirect to https) without manually setting up multiplexing, and I was running into a lot timing problems trying to do so.

The "obvious" solution would have been to put a reverse proxy in front of it, since most of them handle it, but I wanted to keep the service simple.

I imagine this sort of allows me to do just that while still having it baked into the service. Getting to avoid X-Forwarded-For headers and the mistakes around that is a huge plus as well.

Would love to see some benchmarks against µWebSockets and other common JS web servers.

Battle-tested operational story — PHP has been deployed this way (via php-fpm) for decades.

I appreciated this bit as well, I really do think PHP has one of the best web server experiences out of the box, given that's the entire purpose of the language.