3 ms·

Yeah and MSFT showed their stink finger to the community twice, first with C# Managed DirectX, then with end of life for C# XNA. https://en.m.wikipedia.org/wiki

by frik 9y ago

Yeah and MSFT showed their stink finger to the community twice, first with C# Managed DirectX, then with end of life for C# XNA. https://en.m.wikipedia.org/wiki/Microsoft_XNA https://en.m.wikipedia.org/wiki/Microsoft_XNA Who would be so stupid and learn-resistant to use C# a third time for games?? Well there are those sheeps, that believes and do everything for their PR department.

pjmlp 9y ago
They have brought back support for XNA/Monogame when they released the new XBox games program. http://news.xbox.com/2016/03/14/letter-chris-charla-idxbox-updates-gdc/ http://news.xbox.com/2016/03/14/letter-chris-charla-idxbox-u... XNA was a victim of the usual internal wars between Windows Dev and DevTools R&D units, about which way to build software (.NET vs C++). Hence why they are so supportive of Unity nowadays, which is the main way to develop HoloLens applications.
- appleflaxen 9y ago
  > XNA was a victim of the usual internal wars between Windows Dev and DevTools R&D units, about which way to build software the reasoning behind it doesn't change the years of my life I spent learning an obsolete tech stack. which is fine: tech moves on. Except for the fact that MS told me it was the future. and I don't blame them, but I'm also not going to take them at face value again.