Is C# getting old ?
Anyone who may think so got to be insane, but as Wagner pointed out recently..
I think your question shows that C# is just starting to mature. It's the first time I've been asked is C# is getting old. Most of the people I've worked with that are concerned about C# in a new development are worried that C# is too young
indeed C# getting more mature overtime... but is it always mature when it's going old? I don't think so.. some design ideas can destroy the whole big picture.. for instance the first thing i felt when i knew about automatic properties i was like. WHAT.. are they ran out of ideas.. so we got "prop" and the syntax of C# 2.0 is much easier.. and finally C# isn't that complete so couple of team member leave all feature request and start implementing this snippet like feature.
will give you another example, VB on it's .NET version got way mature that it ever was.. and ever since the VB.NET team keep adding new feature.. but recently they have added the XML Literals which will take us back to the classic asp spaghetti code Daniel Cazzulino sees it as something shouldn't be done in the first place:
I see at least a couple drawbacks with this approach:
- VS already has a full-featured, very responsive and cool XML editor that includes intellisense powered by schemas, allows XSLT transformation debugging, etc. We would need to have at least an equally capable inline XML editor in place in order to be really productive
- Now the “template” for the “rendered” XML is compiled into the application. If I need to change anything about that XML layout, I’ll need to recompile the application.
So is C# is getting old, ran out of ideas... I hope not and still don't think so.