Open m50 opened 4 years ago
Sorry for not responding to this. I'll leave my response here in case anyone wants to discuss the same idea.
I'm not personally interested in duplicating all this content in C#. Aside from the additional overhead of managing so much additional content, I like GDScript. I think it works beautifully and is tightly integrated into the engine. To me, the extra overhead that comes with using C# is just not worth it.
It seems to me that C# content here would break down into two audiences:
1) Beginners: If you're a beginner with Godot and/or programming in general (especially in the latter case), you should be using GDScript. Full stop. More language options just adds to the confusion.
2) Experienced programmers (new to Godot or not): You should have no problem applying any of these recipes in the language of your choice. I would still recommend trying GDScript, though - it'll take you no time at all to learn and you may find it as pleasant to use as I do. GDScript is Godot's "reference" language, so you should be familiar with it.
There are those out there in the community who are bigger fans of C# than I, so I'll leave it to them to advocate and promote its usage in Godot.
I think it would be very useful to add the ability to switch between C# and GDScript examples for all code examples. The reason for this is that while gdscript can be a very useful starting point, people coming from other game engines (such as Unity) with C# experience would prefer to use it, and so having more C# code references in our community will help those that are new to Godot, even if not game development. Additionally, if anyone wants to switch to C# for any reason, having code examples that in both C# and gdscript can make it much easier to switch, as they can learn how the two would compare.
Obviously, that's a bit of an undertaking, but it can start small, maybe just a few pages to start off. Could have a C# version of example projects as well for, but probably not necessary to start off with.
I'd be happy to make a PR with C# versions of the code examples, assuming you agree it's good to have them.