Is it worth learning XNA along with C# or should I learn another

File: 1453840259802.jpg (54KB, 600x350px) Image search: [Google]

54KB, 600x350px

>>55579801
Xna is no longer developed by microsoft.

Instead you should learn monogame, which is very similar to xna, is currently supported and actively developed, and is multi platform. I'm working on a win/linux/mac game right now using monogame.

Use vs2015 community on win, and monodevelop on linux/mac. C# is a great language to work with and its quick to develop in. A bunch of fags will praise gamedev with c or c++, but its really not necessary unless your pushing the hardware to its limits. Also, c/c++ dev is slow and error prone.

Fair enough. What about Unity though, I heard it's the shit right now, am I supposed to learn that too?
Also are there any resources that walk you through Monogame, possibly treating you like a 5 year old in the process?

>>55579943
Reimers xna tutorials work for monogame. Just mix and match xna / monogame tutorials.

Fuck. Unity. Seriously. Unity forces you to use their retarded approach to game engines, doesnt allow you to do it your way, and punishes you for using a different design paradigm.

If you want to learn, do it on your own, your way, following tutorials. Start with the msdn screen manager tutorial to understand how to manage game state + screens. Make sure you know how to print to the console so you can debug basic shit, and then just build games. Try and fail alot, and learn. Its really fun.

>>55579943
Give Unity a shot. Does a lot of the backend plumbing for you and tonnes of free and paid content/plugins on their asset store. Bunch of tutorials there too, ranging from absolute beginner to more advanced.

>>55580059
>>55580101
I think I'll go with Monogame cause it sounds a little better. Thanks for your help, guys.