4 ms·

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, an

• NoNameProvided 3y ago
  The target audience also includes Angular developers. NestJS emulates several aspects, such as modules, that it doesn't necessarily need to mimic Angular's appearance. 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.
• flashback2199 3y ago
  This exactly, and Angular also. 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.
• stillbourne 3y ago
  As a C# guy I liked NestJS as well. Like some of the things he describes as hating are the things I liked about it. I wrote a whole ass SAML server in NestJS, it was one of my favorite projects. NestJS is more than just GraphQL.
  • tehlike 3y ago
    Same here, former C# developer, who worked with (as a contributor) Monorail, ASP.NET MVC, Windsor, NHibernate. I feel right home. TypeORM is terrible, however. Prisma is probably way to go.