On: .NET JIT and SIMD are getting married

[kevingadd]

Sorry to break it to you, but .NET has been devouring game programming for years. Unity uses it extensively, XNA was until recently a big choice for indie development, MonoGame is growing, etc...

[npizzolato → kevingadd]

I still don't understand why XNA was discontinued. Is there a suitable replacement for creating games rather easily in C#?

[_random_ → npizzolato]

MonoGame is meant to be an OSS XNA replacement. It's very good for indies with good programming skills. Fez and Bastion were implemented using XNA/MonoGame. If one is more of a game-designer/scripter or is business-oriented then Unity3d is also a good choice.

[gebe → npizzolato]

MonoGame mirrors XNA down to the namespace names so that's a very suitable replacement. You also have Unity of course.

[Guvante → npizzolato]

Completely anecdotal, but I would bet it was due to difficulty getting returns from the program. DirectX itself helps sell licenses of Windows, but XNA not so much due to only impacting indie games.

[Locke1689 → npizzolato]

Unity maybe, but honestly no.

[wtetzner → kevingadd]

I think the "never gonna happen" was about JS and Node taking over the enterprise.

[lern_too_spel → kevingadd]

He didn't say anything about the suitability of .NET for game programming. His post was entirely about enterprise programming.