Programming

C# vs C++ for game programming

it depends on your autism levels

>C#
kek

C# if you want to get a job in game biz.

If you have to ask, then C# and Unity, scrub.

Both, experience with DirectX or OpenGL and memory management is important, and Unity is productive

>unity
Hope you're not referring to the restrictive meme engine

C++

That depends on what kind of game you're making. If you don't expect to run into performance problems, C#. Otherwise C++.

Guessing you're a solo developer. Instead of worrying about languages, you should be looking at engines. Pick the simplest one to develop for that meets your needs. There is absolutely no benefit in making shit more complex than it needs to be.

C++ for Unreal Engine
C# for Unity

are you retarded?

If you want a real job c++ if you don't c#

Except c++ is the only one that allows for memory management. Nobody can take you seriously about memory management using unity

Confirmed for not knowing C# or Unity.

Get the fuck out of here with your dumb-ass.

>memory management

Technically you can do that in C# in unsafe mode, but it'd be stupid and probably breaks Unity's portability.

Amateurs aren't doing anything where they need to write highly optimized memory management systems in the first place. Hell, even professional games and other applications can let the VM manage memory on its own in virtually all cases these days.

this.
You have a pretty good control over the memory used by your game in Unity.
And you can easily optimize it for mobile gaming.

C+ is the best.

C# for pixel indie shit
C++ if you actually need performance

The question you should be asking is nim vs pony

>Instead of worrying about languages, you should be looking at engines. Pick the simplest one to develop for that meets your needs.
This applies to more than just gaming but slightly altered. Fags need to stop posting or asking about languages. Chances are, unless they're doing some exxxtreme shit, all languages can handle it appropriately and in their own way. It's more important people just stick with something, learn the standards, and start making shit. Only after you progress past that stage will you start hitting heavy roadblocks.
And yep about the engine. People need to stop choosing an engine based on what fags online think is kewl. Use what is going to allow you to create what you want in an efficient manner. There's no need to create your own engine because fags on Sup Forums think it's so l33t. Consumers don't care irl (excluding steam forum retards who think they can assess Unity properly meanwhile they think an engine is bad purely because it's old). Unless of course your entire purpose is trying to get an engine programming job.