Readers Weigh In: Sorry, Microsoft Actually Has Our Backs

Are developers feeling alienated from Microsoft? A few articles recently published on ProgrammableWeb center on this theory, and readers are weighing in with their opinions.

In the article "Why One .NET Developer Is Leaving the Ecosystem," author Martin W. Brennan discusses a recent blog post by former .NET developer Justin Angel that explains how he has moved on from the Platform after deducing that Microsoft has "just given up on .net development."

Our readers' responses to this idea ranged from angered dismissal about Angel's position or data-collection methods:

"Let him leave. The article sounds more like that of a bitter person looking to inflict pain to those he feels have wronged him." —Kmcksic (Read the entire comment.)

"He's looking at the data wrong. It's shrinking as a relative proportion of all jobs, but so is Java which is shrinking in absolute terms, as is C++. So his data appears to be bad." —Sign

"Perhaps this is a link bait article, not sure, but last time I checked, C# != .NET. Many languages run on .NET. What about the rise of F#? No mention of that anywhere.

"Things are evolving in unpredictable ways and some 'simple research on job aggregation' on one employment site doesn't mean much to me." —Vincpa (Read the entire comment.)

... to general agreement about the author's points:

"It's a strange turn of events. C# and .NET, and the class libraries are a really nice toolchain. Yet Microsoft found a way to screw it up. ...

"Had they focused on .NET and C#, they would have had a 7 year jump on some key technologies in Android. I was writing mobile apps in Visual Studio, drag-dropping classes between client and server layers, in C#, for a Compaq iPaq running Pocket PC and .NET Compact Framework, connected to the Internet on an Ericsson 2.5G (GPRS) handset. As nice as Android is, you can't achieve the same level of toolchain unity with Android and Google App Engine even today." —Zigurd Mednieks (Read the entire comment.)

"The author does make some good points. Sometimes, .net development feels like you are building on sand. As soon as you build a website with web forms, MVC becomes the standard, etc. But, MS is more responsive than ever. Their MVC is fantastic and continues improve. It's hard to strike a balance between obsolescence and progression and MS seems to be doing a decent job.

"I can't blame someone for switching jobs, but C# and .net are reaching their prime. Perhaps the jobs aren't as plentiful, I have no idea, but as long as I'm not programming in PHP, I'm happy." —Masilver

... and then on to a discussion about client-server architecture and API design:

"It's only a matter of time before software production moves into that same realm, and MS is been beating VS into that mold now for some time. Does that mean .net is going to be the key or not key hard to say. I wouldn't be surprised if they didn't fall back to a c++ unified language. Overall though each client technology has it's plus and minus, they all have a means to exist and each does something specific very well. It's more a trend that developers are being asked to know more than just one language now, not that any language is in trouble over the other. The hybrid Stack is where it's currently at, maybe we will get lucky though and push it back to a set unified stack, if we could ever get so lucky. Out of all the players MS is the only one attempting to do that though, so we will just have to see where that falls." —Mtcoder (Read the entire comment.)

"... while the client side could eventually settle on the Web stack, I don't see that happening any time soon on the server side. That said, what I do see is a pace of innovation when it comes to dev tooling and devops that is quite frightening..... creating an element of doubt when it comes to committing to anything. This sentiment is captured quite nicely here." —David Berlind, editor in chief, ProgrammableWeb (Read the entire comment.)

In another article, this time by ProgrammableWeb Editor in Chief David Berlind, readers have commented on whether or not the fact that Microsoft is forking Node.js should be of concern.

Most commenters are open to the idea:

"Has Git been destroyed? Microsoft are contributors to that project as well." —Steveski74

"This is quite the hit job. The readme for the fork *clearly* indicates that they intend to contribute this work (to make the JS engine used by Node to be pluggable) back to the main Branch. Basically they're making a great contribution to the Node community and doing it in exactly the standard way that open source projects work today.

"Having the engine be pluggable is really valuable. It means Node gains independent implementation of the ECMAScript standard. It means better support for non-Google platforms (e.g. JIT on iOS via JavaScriptCore could build on this), and that developers can get better support for ES6, for example, and the better performance offered by Chakra over V8.

"I don't see any basis for the fear-mongering you and Winer are pushing here. If Mozilla did exactly the same thing, I wonder how you'd have reacted." —BrandonLive

"Their [Microsoft's] support of node and the node community has been huge and it's sad how few people realize it. Windows Azure has some of the best node support you can find. It was one of the first hosts to support both node, Websockets, and Continuous Deployment all at once." —Chevex

What do you think? Are programmers beginning to shy away from Microsoft, or is Microsoft making all the right moves to keep existing developers while recruiting new ones? Let us know your opinion by posting a comment here or below the articles mentioned above.

Be sure to read the next Languages article: The Most Popular Programming Languages According to ChargeBee