Request docs: Why chose Danet over NestJS?

[NfNitLoop]

Is your feature request related to a problem? Please describe.

I'm learning NestJS. I happened to see Danet when reading up on NestJS compatibility in Deno. But, given that NestJS now works in Deno, I'm wondering Why would I chose Danet over NestJS?

Describe the solution you'd like

Docs somewhere answering the above question.

[chillbrodev]

As software evolves, developers face a choice: continue with familiar tools or explore new paths.

Why Consider Danet?

• Native Deno Experience: Deno makes TypeScript truly enjoyable - no complex setup, no node_modules, no build steps, no TSConfig. Updates are seamless.
• Modern Architecture: Danet leverages Hono (a fast web framework) and embraces Deno's first-class ESM support, rather than Node's CommonJS roots.
• Performance: According to Danet's creator, "Danet performs better than node+express thanks to Deno+Hono performance, despite our code overhead."
• Future-Focused: Created by Ryan Dahl (who also created Node), Deno represents his vision for addressing Node's shortcomings.

Why Stick with NestJS?

• Maturity: NestJS is battle-tested with a larger ecosystem of modules and extensions.
• Community: Much larger community means more resources, tutorials, and Stack Overflow answers.
• Completeness: Danet isn't yet a 1:1 match for NestJS functionality.
• Integration: Better compatibility with existing Node.js codebases and libraries.

The NestJS CLI doesn't natively support Deno - you can get NestJS + Deno to work with some extra effort.

Ultimately, it depends on your goals. Learning either will provide valuable skills. If you're focused on production-ready applications with extensive ecosystem support, NestJS might be better today. If you want to embrace the future of TypeScript development with better performance and security, Danet is worth exploring.

My recommendation? Learn both if you can - that knowledge will give you the perspective to make informed decisions for each project's specific needs.

Bonus: Here is some information from the Danet creator they posted on Reddit:

When running on Deno, Hono still performs better than node+express. 
And Danet does too thanks to Deno+Hono performance, despite our code overhead.

Using npm packages or node compatibility is a last resort when using Deno. 
The point is to use Deno first packages to get all the benefits.

Don’t get me wrong, I love Nest. I just like Deno more and want to give it its own awesome framework.

[airtonix]

Yeah but we can just use hono with nestjs.

Also I doubt the friction to using nestjs under deno is worth sacrificing all the maturity of nestjs.

[Sorikairox]

Same could been said for Node vs Deno 😉 Danet was created when Deno's goals were to NEVER be compatible with Node or NPM.

It has changed, so do what you want, I will keep having fun maintaining the project and making sure it's the best Deno first backend framework 😘

[itizarsa]

@Sorikairox, I am just curious: How are you planning to maintain the framework since Deno deprecated the experimental decorators?

I'll choose Danet over NestJS anyday on Deno, coz Deno won't be the priority for the Nest team.

[Sorikairox]

There isn't any alternative to TS decorators (JS one are really bad in terms of DX).

So I doubt they will remove support entirely soon. It will trigger to much backslash IMO.

[chillbrodev]

Same could been said for Node vs Deno 😉 Danet was created when Deno's goals were to NEVER be compatible with Node or NPM.

It has changed, so do what you want, I will keep having fun maintaining the project and making sure it's the best Deno first backend framework 😘

Thank you for continuing to work on this. Having a Deno First backend framework is core to Deno's Success.