Unit 20 · Language valence 2: C# on Hacker News · q27b

It’s wild to think that 10 years ago people were still arguing about whether C# was "just Java with generics." Now it’s arguably the most productive language for building high-performance, cross-platform backend services. The ecosystem maturity is just insane. --- The real story isn't the language features, it's the tooling. Hot reload in production, seamless deployment to Linux containers, and the fact that you can write a full-stack app with Blazor without touching JavaScript is a massive shift. Microsoft really nailed the developer experience here. --- I miss the days when "C#" meant "Windows Forms and SQL Server." Now it’s everywhere: game engines, IoT, cloud-native microservices, and even mobile. The only downside is that the learning curve for the new async/await patterns and dependency injection containers has gotten steeper for juniors. (greedy generation)

I’ve been writing C# since 2016, and honestly, the biggest change isn’t the syntax—it’s the culture. Ten years ago, if you mentioned C# outside of a Microsoft shop, you got blank stares or "isn't that for enterprise bloat?" Now, I’m seeing C# in startups, in open-source CLI tools, and even in high-frequency trading firms that used to be strictly C++ or Rust. The language has become incredibly pragmatic. They’ve stopped trying to be everything to everyone and focused on making the common case *just work*. Pattern matching, records, and top-level statements have cleaned up so much boilerplate. But the real win is the performance. .NET 8/9/10 (depending on how you count) is fast. Like, "why are we still debating this?" fast. That said, I still cringe when I see teams over-engineer with MediatR and CQRS for a simple CRUD app. The tooling is so good that it’s easy to fall into the trap of adding (greedy generation)