I for my part want c# for its incredible extensibility and foremost for its faster development process.
I work much with procedural generated content. While developing i dont care much about calculation speed (since my rig is a fast one) and its much easier and faster to try out things in c# than in c++ because of the .net libraries/nugets etc and because with klawr it’ll be like its scripted. You change the code and then you’ll see the result a few seconds later.
I have to write less and the error messages in c# are always spot on (not always the case in c++). I dont have to manage header files additional to my code class files (which is a pain in itself, but thats another problem i generally have with c/c++).
Development speed, thats a main driving factor if you try something new with a yet unknown result. The process of optimization (speed and/or memorywise) comes after that for me, because something i cant code in c# i wont be able to code in c++ either.
The blueprints in UE are very nice, but they’re also not suited for complex calculations. They have to be coded.
TheJamsh isn’t wrong if he tells ppl to learn something new (thats never wrong), but for me c#'s pro’s (RAD, easy extensibility, vast number of libraries and reflection) are clearly more important than c++ strengths (mostly speed)