Re:Windows NT Kernel Contributor Explains Why Performance is...
by illuminate on Saturday May 11, 2013 @12:05PM
(#5691025)
"XNA was canned while Microsoft left MonoGame and Unity pick up the C# developers still willing to invest into the platform"
I have no insider information to suggest otherwise, but don't you think that a replacement will be released with the new console?
Re:Windows NT Kernel Contributor Explains Why Performance is...
by bentcorner on Saturday May 11, 2013 @01:06PM
(#5691242)
My gut feeling is that even if they do, indie developers aren't going to fall for that one again.
Re:Windows NT Kernel Contributor Explains Why Performance is...
by ams6110 on Saturday May 11, 2013 @01:48PM
(#5691371)
What choice will they have?
Re:Windows NT Kernel Contributor Explains Why Performance is...
by cpleppert on Saturday May 11, 2013 @01:47PM
(#5691369)
No because microsoft isn't going to support a toolkit it has no intention of using on mobile or the desktop and will never be used by commercial game developers.
Re:Windows NT Kernel Contributor Explains Why Performance is...
by pjmlp on Saturday May 11, 2013 @06:06PM
(#5692278)
Are you aware there was a Premium version of XNA for AAA studios?
Re:Windows NT Kernel Contributor Explains Why Performance is...
by eropple on Sunday May 12, 2013 @12:35AM
(#5693166)
As far as I know, the XDK Extensions were intended for XBLA developers, not "AAA studios".
Re:Windows NT Kernel Contributor Explains Why Performance is...
by pjmlp on Sunday May 12, 2013 @01:50AM
(#5693306)
It was announced in a different way at a Meltdown or PDC conference, around 2008 if I am not mistaken.
Sadly those videos seem to no longer be online after MSDN was redone.
Maybe someone can correct me if I am wrong.
Re:Windows NT Kernel Contributor Explains Why Performance is...
by illuminate on Saturday May 11, 2013 @04:51PM
(#5692063)
"a toolkit it has no intention of using on mobile or the desktop"
Right, I find it likely that XNA was killed to work on a better toolkit for all three.
When Windows Phone 8 came out, the native renaissance was full speed inside Microsoft, C++ with DirectX became the official way and XNA was canned while Microsoft left MonoGame and Unity pick up the C# developers still willing to invest into the platform.
The sad thing is that this is not a native vs managed issue, because even C# gets compiled to native code when targeting Windows Phone 8. Just plain product management decision to kill the product, which was being sold as the way to develop Windows Phone games.