If they had a team that knows nest and can iterate fast with it that's the perfect choice

Same experience here. C# might have superior tooling, performance, whatever but the OOP baggage is too heavy. In theory you can write something else than a giant over-complicated, over-abstracted pile of OOP nonsense in C#, but every team I've seen has .

> ...because it assumes that a C# team could have delivered the initial version in the timeline required to get to the the next level of project. I linked the Nest.js project because you can see how similar these two are[0] with Nest.js leaning into the OOP aspects of TS at the very core. Controllers and services are classes in Nest.js, for example. It uses a somehow more complicated DI system than ASP.NET. It is Spring Boot or ASP.NET, but without the maturity, performance, and ergonomics. The team had developers that had done C# before and later hires also included former C# developers. TS itself was new for the team at the time and several mistakes were made along the way resulting in a "dual-ORM" situation (Prisma + Drizzle; both with their faults) that ends up sapping a lot of productivity (one of the drivers to move to C#). [0] https://typescript-is-like-csharp.chrlschn.dev/pages…

Hmmm. I have a different take there: when you are young and wild, you achieve stuff because you think later and instantly produce code. When you turn older, you do it the other way leading to your example. In the early 2000s I have been in a startup and we delivered rapidly in C# as we did in PHP. We just coded the shit.