You can always tell you're dealing with a junior-level programmer when they complain about new syntactical sugar added to a language. I've been programming alm

You can always tell you're dealing with a junior-level programmer when they complain about new syntactical sugar added to a language. I've been programming almost entirely in C#/.NET since its beta in ~2001, and though the language has obviously evolved significantly since then, it still feels like the same core. The language features were never an issue; it's the ephemeral feature frameworks that can be frustrating (e.g. WCF, WPF), and of course, the whole .NET Core/Standard/Framework confusion. However, that is easily tempered by the fact that .NET moved glacially compared to the 'hip' languages, and support is offered for older tech for years/decades. The last few years have brought the seamless ability to run .NET on Linux, a built in, super-fast web server, support for gRPC, fully open source, and massive performance improvements. It's never been the 'cool kid', and it has its baggage from years of MS being MS, but I'm hard pressed to think of a better choice today for writing a large, reliable, and performant web application. C#/.NET probably rivals Java in the billions of lines of code out there, written over the last 20 years, driving critical business processes across many sectors. It's not going anywhere anytime soon. There's not even a reasonable contender for migration for all those 1MM+ LoC 'boring' applications out there (unless you flip to Java.)