Post

I have a private repo and matching npm org called "h3xt" I registered yeas ago. Never pushed the code to it, but it was intended to be somewhere between your H3 and express. Web standard api's but with the the middle approach. Funny naming coincidence.

Ah thats funny! We also renamed org from httpjs back to h3js because could be so confusing with jshttp 😂 Curious to read what was your original idea in h3ext ❤️

It was web standards based spiritual successor to express. So keeping some of the same middleware first designs, but using web api's and tightening some of the obviously bad parts historically in express. Honestly though, I realized that it would be better to just land those in Node.js/express.

Why tho? Frontend standard used for a server on Node.js makes no sense.

Interop makes sense. And other platforms are adopting these. I hope we can land support in Node.js and tried to get that work started but it never really got its legs. (Reposted because I just woke up, am in bed still and it barely made sense when I re-read it lol)

For high scale/performant web servers though, might be a tough sell over more optimized APIs. But we need to also land those optimized approaches in Node.js before anyone will take that seriously.

link to the benchmarks? This doesn’t match my numbers.

github.com/h3js/srvx/tr... Benchs are farily simple. We also cheat somehow by adding fast path for response and a two way proxy of interfaces — pretty surre could be much better done natively in Node!

If I understood correctly, your benchmark is using FastResponse and not the default Response object, right? What’s the gap with using Response? Would you mind sending a srvx-fast bench to github.com/fastify/benc...?