Why Choose NestJS as Your Back End Framework

amplication.com

2 pointskevinslin4 comments

My company uses it. I really hate it.

JavaScript world has moved away from classes. NestJS brings it back with a vengeance. It makes things so complicated.

I do passionately hate how DTO can’t be types or interfaces, but AFAICT this is the typescript type-checkers fault and not Nest’s. I’ll gladly take my ability to auto-generate service client libraries for all of my micro services while never touching an OpenApi document, thanks to Nest.

I don't mind some of the magic it does but using dependency injections and classes is just weird and adds complexity and boilerplate.

Not to be confused with NextJs, the React framework

Be careful of clueless HR that confuse those two and accidentally recruit you for the wrong framework

Reply on news.ycombinator.com