FNA VS Monkey 2

Emulating "dead" consoles and unchanging APIs is usually sustainable. We'll all be able to play Sega MD/Genesis games and XNA games until the end of time, with whatever hardware, platform, controllers, and video outputs we need. Source: about 1 year ago

Https://fna-xna.github.io/ this explains it better. Source: over 1 year ago

MonoGame is an open-source framework, a thin layer of abstraction over input, sound, and graphics APIs. MonoGame lets game developers write cross platform code that will run on desktop, mobile, and console devices. Many commercially successful indie games have been shipped using MonoGame, and it's similar frameworks XNA and FNA, since 2007. MonoGame is ideal for developers who don't want an engine to dictate their... Source: almost 2 years ago

FWIW while this tutorial series looks very old and XNA has indeed been officially discontinued, FNA is a 100% compatible (or at least as 100% as it can be :-P) XNA reimplementation that can be used instead of XNA and is still under active development (last release 11 days ago) while it has been used by a bunch of games already. Because of that most XNA resources should apply to FNA too. Source: almost 2 years ago

So a little bit of context here: I'm a huge fan of the FNA game framework. It's an open source replacement for the discontinued XNA 4.0 framework. I think it's fantastic for small scale indie projects, it's such a nice blank canvas "only the things you need" approach. Source: almost 2 years ago

On one hand, BlitzBasic and BlitzMax was a key moment for me, 15 years ago, of 'getting' programming - I clearly remember as a teenager when some basic concepts clicked together, and here I am many years later a full-time indie game developer. But on the other hand, I've watched from afar enough of the post-Blitz tool development to be skeptical of anything new. Monkey 2 and Monkey X really didn't flourish and a... - Source: Hacker News / almost 2 years ago