@yavor-kirov

Glad you find it helpful!

Here is a Reddit topic
with some comments from romainlanz
that has some of my comments too https://www.reddit.com/r/node/comments/1ok6g7y/what_would_you_choose_nestjs_or_adonisjs_and_why/ I wrote it better there I think (username Appropriate_Junket_5)

hope that's helpful

good luck!

Adonis seems great so far. Adocasts is also quite great. They both feel a little unpolished but it takes time to reach that level. I've been using Laravel for quite some time and I remember the 'not-polished' times :)

But the main thing I'd like to say is: Focus on the WHY? of the framework. Tell people why actually this is done in this way and why it is awesome! :)))

What I mean?

I find it very entertaining (and a bit sad) that nobody is talking much about the philosophy of the framework. Adonis clearly places "Convention over configuration" and a lot of work is going into "developer experience". This makes it UNIQUE in the Node.js world. It comes up as 'different' and even 'weird' if you don't know why things are done the way they are.

I am a big fan of Laravel (And Rails when it was "up-to-date" because by renouncing modern FE it hasn't done itself much service…). I cannot understand why the Adonis team and this video do not speak up about why Adonis is the best choice for startups and small and even mid-sized companies (probably to at least Shopify-level-big companies, and that actually is more than 80% of the companies out there!!!). Is the Adonis team afraid to state that a monolith-batteries-included-framework-that-can-do-it-all is actually something awesome? Awesome because it saves devs a ton of time! And time is the difference between your startup/business making it or not. It's important what the philosophy is. For example: Nest.js - pretty much the framework with the most github stars for Node.js … it has a very different philosophy. It's much more 'configuration over convention' and it cares little for Developer Experience. It pulls successful packages from the Node.js but does not care to make them compatible. Just some "glue" code to make it all work. Also with Nest.js a developer is burdened to choose packages. Nest.js is not really a 'batteries included' framework. There are many proofs of that. I think that many people come from places like Java or C# world and expect to find something that forces you to write lots of boilerplate (like Nest.js does).
I feel that the power of Node is exactly the reverse. It's in writing less code. It's why actually the Node.js came into the spotlight in the beginning. PayPal rewriting their codebase from Java to Node made their code more performant and it was less code. I remember that 'incident' as a big part of how Node.js got to be advertised. Nest.js is pushing to make a new "Java Spring" out of Node.js. So basically Next.js is pushing in the reverse direction of what Node.js' strengths are!

I would be very happy to see you guys give some advertising to the concepts of 'convention over configuration' and DX. If you want to know more (or steal an idea or two, or get inspired?) … DHH is the GOAT there. Taylor Otwell (laravel's creator) is great at implementing the concepts but he is not much into talking. So i feel DHH is a better suggestion here. He has many talks and interview in youtube ranting about why he made Rails the way it is.

Good Luck!!!