I believe the target demographic for NestJS are spring developers, not native JS/TS developers.
If you come from Java / Spring you would feel right at home, anyone else would feel disgust.
If you come from Java / Spring you would feel right at home, anyone else would feel disgust.
I cannot pass judgment on whether this is good or bad, but I can easily see how this familiarity can be beneficial for the average programmer.
TypeORM is terrible, however.
Prisma is probably way to go.
It is pointless for the author to argue about the best way to use TypeScript because the value proposition of NestJS is to use the same patterns as another framework you are already using.
If you're building a React app, for example, then NestJS doesn't make as much sense, it's just going to feel like it's getting in the way, hence this article.
This article really misses the mark and the author is just proving that they still don't understand what NestJS is for.