Comment Re:No thanks (Score 4, Insightful) 242
Unfortunately, C# suffers from a sort of fragmentation where every year there's something new and fresh with it. Even though you and I, as developers in the wild, understand that this "fragmentation" is a bunch of hype and circumstance where the underlying base and syntax hasn't necessarily changed much over the past 3 years, the technologies around it have changed significantly.
To give an example, just today we ported an in-house app that is a tool to help with debugging that was updated at the very end of 2013 and ran on Server 2008 no problem to a new environment running Server 2012. Just about 2 weeks over a year after its last rewrite, it took about 20 minutes to install "legacy" packages on the server where it could be shoehorned in as Network Service
Other examples are abound... Such as our desire to update several of our apps to take advantage of new features in MVC 6... but other features that we relied on in MVC 4 and MVC 5 broke, so there's a heavy need to develop work arounds or find "the new way to do it" (tm). Also, management wants us to implement Entity Framework 6 for our new database connections rather than use LINQ as we had been...and as we have time, update some of our older and more critical applications to make use of these new frameworks as well. And just wait for the next round of "Oooh Shiny" that we are going to want to make use of this year.
The technologies packed around C# and
If you want to have a language background where you can take 2-5 year hiatuses from it and still maintain a decent demand with it, learn straight C/C++ and COBOL. Where I work I command among the highest programmer salaries in my department not because I'm good with the current tech and keeping up with it (my perf reviews have always indicated this to be true), but because I save my team from having to submit a WorkRequest to the Mainframe Developers for quick batches. My team can tell me what they need and I can submit my time bid and process to the Datacenter Operators in half the time with only one sheet of paper used for signoffs and approvals(instead of 5)... just because I can actually write COBOL (apparently hard to find in anyone younger than 40 these days, and our last COBOL Programmer is slated to retire in 2018).