Why One .NET Developer is Leaving the Ecosystem

In the ever-changing world of coding, one particular developer has decided to turn his back on the .NET Framework to move onto newer, more promising technologies. In a recent post, Justin Angel discussed why he is moving on and offers advice for other .NET developers.

Angel spent the last dozen years in the .NET ecosystem. He even helped to build it during his time working at Microsoft and Nokia. However, his recent experiences and research has led him to some fairly stark conclusions. The most startling being the plummeting rate of jobs around the Microsoft developer ecosystem.

According to some simple research on job aggregation site Indeed.com, there has been around a 60% reduction in C# jobs since its peak in 2010. This is backed up by around 50% drop in C# developer interest since 2012, according to the TIOBE developer interest index. However, for Angel it seems that the root cause is Microsoft itself.

Firstly, with iOS and Android taking up 90% of the worldwide smartphone market, .NET developers have little room to compete. But it seems that Microsoft’s “ever revolving door of new technologies” is the driving force behind the decline thanks to so many new products and technologies being ushered in with little regard for what came before.

Most recently, Angel noticed that in Microsoft’s Azure Documentation, .NET is on equal footing with Node.js, Java, PHP, Python and Ruby, and he feels that Microsoft has simply given up on .NET. That is why he has chosen to move on to a full-time position using Java as an Android developer.

The author admits that he may be wrong, but he also worries that he is right and encourages other .NET developers to seriously consider their future. With so many popular non-Microsoft frameworks and the rise of mobile platforms, developers have a multitude of options available if they wish to pivot their careers and keep current.

Be sure to read the next Developer Relations article: Twitter Founder Admits Error Over API Rate Limits

Original Article

The Collapse of the .Net Ecosystem