3 ms·
Well free stacks aren't really free either but we could argue that point until we're blue in the face. The issue with Microsoft right now is they seem to want
by TomOfTTB 15y ago
Well free stacks aren't really free either but we could argue that point until we're blue in the face.
The issue with Microsoft right now is they seem to want to throw away everything they've created over the last decade and embrace the web in a desperate attempt to bring new developers in.
For example, if you watch the Build sessions you see a lot of focus on C++ where as Microsoft used to treat C# like it's preferred language. That's got a lot of people thinking Microsoft's looking to sideline C# in the same way they did VB 10 years ago.
Visual Basic was obviously more popular that C# at that time (being C# hadn't existed before that). So the Tiobe index doesn't mean much (and honestly I'm always dubious of Tiobe in that I don't think PHP is more popular than Ruby and Python combined in modern development)
3 years ago Microsoft was telling developers to use ASP.NET Web Forms, WPF, and Silverlight. Today all that is essentially looked on as bad practice. So yes, there are people in the MS Developer community who are nervous.
- runjake 15y agoI did watch many of the BUILD sessions, but never saw any indications that C# was going away or even being de-emphasized. I think you may be misunderstanding. Could you give examples of what you mean? Microsoft isn't really "throwing everything away", they're shifting product strategies in a rather confusing and convoluted way. However, the latest stuff their pitching is C# and stuff from Silverlight (even though it's "dead") -- it's largely the same technologies. A Silverlight or WPF programmer will find a relatively painless transition to WP7 (which is essentially WPF/Silverlight) or W8 Metro apps. I think your idea that C# is being de-emphasized or going away is a very, very incorrect statement contrary to reality.