> And .NET is the language of choice for "Enterprise". So that's what the majority of jobs are.
Disagree. I would argue Java is more of a choice for "Enterprise".
Also, would you please define the scope of "enterprise".
If you mean "enterprise" as someone who want consistent and predictable management and productivity, then sure .NET is "enterprisy", because instead of a dragon they want a fossil.
But if you mean "enterprise" as they want to sell their core product, and sometimes that pushes to high developmental velocity with multiple development team to tackle on a feature, then .NET is evolving fast enough that it is not so considered "enterprisy".
Heck, even Ruby on Rails would replace .NET for that, especially when you consider the e-commerce scene that is either Ruby or PHP (Wordpress).
Just look at C# and its incredible language revision every year.
> I would argue Java is more of a choice for "Enterprise".
.NET was literally created to replace the Java enterprise ecosystem. It never managed to completely displace it, but effectively gained around half of the enterprise market - and it will take more and more, after Oracle started pulling their usual boa-constrictor moves. C# is as "enterprisey" as they come, and it went full-opensource only once it became a requirement even in the enterprise.
It is mostly an Enterprise Development complaint... that said, it's how most .Net shops are in my experience. I really like C#, I've been working on a project with FastEndpoints and the .Net 10 RC since April and been pretty happy with it. That said, I don't have to implement 10 layers of indirection/interfaces/patterns to get the job done either. I have in other places.
But I would levy the same complaint with most Java[1] usage as well.
Where as large 'tech' companies don't tend to be like this.