For those who didn’t get the Monty Python reference…Microsoft has just killed another one of it’s own technologies. The latest to join the heap…XNA!
For those not in the know, XNA was an API that allowed you to develop games for “Games for Windows” (deceased), Windows Phone 7+ (might as well be deceased) and X-Box 360 (surprisingly still a contender) through a common library using Visual Studio. It was to replace Managed DirectX (deceased) as the go-to Game Dev tool for the Microsoft Platforms.
I had dabbled in XNA version 2.0. I can’t speak from recent experience but from what I remember, it wasn’t a terrible library. I do remember a lot of headaches stemming from compatibility issues that came up when they would release an update, i.e; from 2.0 to 3.0. This foray into XNA was during a phase in my life when I thought trying to start your own Game Dev studio was a good idea…
This brings up a conversation I had with another developer a while back. Basically, I was working at a Microsoft shop at the time (on life support) whereby the other developer was saying how using a dev stack that had the backing of someone like Microsoft is far better than anything the Open Source Community has going for it. This came from me bringing up the fact that Silverlight was going to die (deceased) dragging all the WPF (deceased) and XAML (deceased) stuff with it.
My point in all of this is that despite companies and organizations looking for “experts” or “gurus” in a certain technology, it is CRITICAL that you avoid this and try to know a few different languages/stacks. I mean, think of the developers who spent so much time, money and effort learning things like Silverlight (deceased) or Flash (deceased but not Microsoft).
*Begins Playing Amazing Grace on Bagpipes*
Lest We Forget…
Windows Phone 7
TypeScript (c’mon you know it’s coming!)
WebMatrix (the first one for sure)
Linq 2 SQL
May you all find ever-lasting peace in that great code repo in the sky…