I've worked with the C#/.NET platform for a number of years. As OP points out it has a lot of cool features. But this can also be part of the problem. When you have a big team working on an Enterprise project (which is probably this stacks main audience) you always seem to end up with people who love certain parts of the language and hate others and as a result it makes it difficult for people to work on each others code because theres so many features and not everyone wants to take the time to learn everything when they already have their core set of features that work for them.
It is great that it improved upon what Java was lacking, but I think the C# team is starting to go too far adding too much.
What exactly seems too much? C#'s feature set doesn't seem that expansive. I'd be upset to be forced to deal with a least-common-denominator subset because someone doesn't understand, say, closures.
But I've not worked on an "Enterprise" project, and I assume the main goal there is making sure you can hire anyone and make sure they can understand how to add a new rule for e.g. Alaska sales tax.
Sounds like an issue with process. Is there no code review or coding standards document or collaboration in planning "what is the best way to do this"?
It is great that it improved upon what Java was lacking, but I think the C# team is starting to go too far adding too much.