Very interesting how discussion turned out 
I will add my two cents, since I believe that we should encourage a different mentality than it was shown here.
I have been using C/C++ for a long now and due to my work I started using C# a while back. At my workplace, we have been using the many tools out there you can combine with C# and Visual (e.g. resharper) or libraries that come with it (e.g. entity framework) - speeds up and simplifies many development steps remarkably lot. . C++ is much more tedious than C# is and quite bloated through those changes and revisions. But every now and then when I write code, I feel like it would be much easier in C++. is almost always the case when I care about performance or want to code closer to the hardware.
So while I favor both languages and would be quite happy if UE supports them both, I still think that the very discussion of leads nowhere anymore. But even then, we have a group of people here who would like to code in C# and they should still be allowed to post a request in the forum the same way else is allowed to request features they would like to see. But the way unfold months ago, the thread was trashed and users nearly tried to defame the poster and very idea as if they wanted to kill its appeal.
The pros and contras regarding the programming languages were listed quite detailed, so at least I will not make the mistake to repeat anything. But matmuze should nevertheless be allowed to try to appeal to the epic team.
@matmuze: I agree with you that it is easier to use C# and that it may lead to more productivity.
But you need to face two facts:
- UE is around since 1998. It is entirely written in C++. If you really wanted to profit from the open sourceness of UE, you would need to get comfortable with C++ anyway. You will need to access its source code if you really wanted to make the engine your own - or request that the Epic team converts its whole project to C#, which would be very futile and a huge waste of .
- UE is an engine, its not a tool. Whether you code in C++ or C#, you will need to get familiar with the Engine and its facettes. Whatever you want to do with the engine, 90% of the you will access the engine code and execute the functions and use the classes and structs that the engine provides. You will also have to use their macros - whether you are in C# or not. Because in the end, the project you create will be just an extension of the engine - or rather, the engine will be part of your game. You will have to dwelve into the documentation, learn about the engines terminology and look at the API of the classes you might need for your project. is a step that you will have to go through no matter which scripting language you use and can not be skipped. And most of the - unless you really want to extend the engine by new features - the only code library you will use is the engine itself. It is true that C# is easier in many cases, but in case - if we judge it by probability - it will probably be of no real value.
Just for those two reasons, I think there are many more important features that the epic team should care about.
I suggest that we let matmuze and kindred spirits speak for themselves and give them the to appeal to the epic team for as long as he wants instead of trying to silence him. is after the forum section for feedback and different opinions should be allowed here. Any further discussion from the opposition will be useless unless the epic team resonsiders whether to reject the idea or not. So to those people still opposing idea: Chill and allow other users to be. is probably what the epic team would like us to do as well. (I guess)