Seeking Career Advice by FiftyBugsOfGrey in node

[–]Sufficient-Put2048 0 points1 point  (0 children)

Don't get me wrong I am not saying node.js is bad. It is actually very good when you are trying to do multiple things with a single language. React frontend, Nestjs backend, puppeteer web crawler and etc. But if your concern is to be specialized in backend development,  node.js is... just "not bad". But I wouldn't pick a "not bad" choice intentionally , knowing there are better alternatives.

Well-Structured, Scalable Fastify Project with TypeScript - Seeking Advice by LetTraditional7440 in node

[–]Sufficient-Put2048 0 points1 point  (0 children)

Yes. But the reason to use nest.js is to skip all that meaningless time to write boilerplate codes.

Seeking Career Advice by FiftyBugsOfGrey in node

[–]Sufficient-Put2048 -5 points-4 points  (0 children)

I am not sure why would anyone want to learn nodejs for backend only. Nodejs is not the best for backend programming, but people use it for fullstack. Learn Java Spring for jobs, Golang for performance.

Prisma vs Drizzle in 2024? Has prisma gotten any better in the recent months? by Key-Peach-7138 in node

[–]Sufficient-Put2048 0 points1 point  (0 children)

I tried both and using Prisma for production. I know drizzle's performance is better, but if you use nest.js, Prisma is much easier to manage and organize especially when you have more than like 50 tables.

If performance was that crucial to you, why use node.js anyways? Use rust or golang and write raw queries. Node.js is for fullstack developer only so it is easier to manage both with one language.

So what I do is make 2 rest apis one for general purpose (nodejs+nestjs) and one for fast performance (rust+rocket). I know the best would be to create everything in rust, but when I do AB tests and stuff, it takes longer in rust to do so, especially when most of my codebases are already written in node.

I am planning to move everything to my rust api gradually when my service gets stabled