ditsmod / vs-webframework Goto Github PK

what do you think on adding another version of nestjs+fastify that doesn't uses the request scope since we know that this minor change will impact the performance?

Since we couldn't have a new Ditsmod version that doesn't uses the Res, I'm unsure if this comparison will be fair tho.

(later I notice there are discussions in the ditsmod repo, which is a better fit for this kind of feedback)

So, there is a common belief in node.js that Fastify is the fastest framework, why would they put "Fast" into their name otherwise, right?

But actually, there is a much faster framework called uWebSockets. It's a terrible name for marketing because you expect it to be a lib for websockets. And no clue regarding its speed. But actually, this is the fastest node framework that even beats Bun (see benchmarks here) and it's not supported by Bun (explanation here).

Btw, Ditsmod is also a bad name, the good name should be simple and rememberable, like Bun, or should tell us what's so special about it - "Fast" in Fastify.

So what I'm proposing:

1. base Ditsmod off uWebSockets
2. make people believe it gives all the same benefits as Nest, but easier. Instead of comparing perf with Fastify, better compare usability with Nest, as Nest is the target auditory. I haven't read the docs of Ditsmod yet, to be honest, but AFAIK Nest, there is a big room to make it simpler.
3. compare Ditsmod with what people believe is the fastest - Bun! If the framework overhead is minimal, it should beat Bun thanks to uWebsockets. This will give hype.

I'd really like if there was a framework similar to Nest but simpler (Dismod looks even more verbose tbh) and much faster.