I disagree. Even if one is new to programming, learning GDScript still teaches one how to program. Loops, conditions, variables, functions… basically all that is programming is still part of GDScript and it would be no more difficult, once learned, to switch from GDScript to any other language as it would to switch from C#, C/C++, Python, etc. That is to say, once you understand how to program, it’s nowhere near as hard to switch languages as initially learning your first one.
That said, the same could be argued when working with different engines within the same language. C# in Unity, C# in Godot, and C# in ASP.Net applications all have their idiosyncracies that might make the language feel different, even though, at it’s core, it’s the same language. How a library functions can have a drastic effect on how you program a language, and if you change one library for another, even in the same language, you may find you have to alter your programming style.
Additionally, languages can be ported. GDScript currently only exists in Godot, but nothing is stopping anyone from writing a python-like or nodejs-like runtime interpreter for the language that allows you to use GDScript sans-Godot.
As for how nice the language looks… that’s subjective. I, honestly, find GDScript to be a very clean looking language (much like I do Python… probably unsurprisingly). C#, on the other hand, I find to be a verbose mess, seeming to take 100 lines of course to accomplish something I can do in 10 in other languages. But, again, that’s subjective
Personally, I like the idea of using bindings more than using GDscript* in Godot and my preferred language outside of Godot. From what I’ve seen, even if not perfect it’s much less likely to cause confusion having 1 workflow (+some extra context in Godot) rather than 2 (not just syntax, but also technical stuff). Also it’s nice to use code that doesn’t actually depend much on whatever engine/framework you happen to be using it in (particularly an imported file with procedures).
Though some of my perspective may be that I haven’t really used the language that I want to (mentioned in other comment) aside from a bit of tinkering with Raylib bindings (and a bit with Godot 3.X), so (aside from switching back-and-forth making less sense) I need Godot to learn the language just as much as I need the language to use Godot, all the things that motivate me (starting points for projects) are in various stages of viability particularly with how they relate to each other. Which admittedly is not the type of situation people wanting C# are in (…maybe some are with 4.X C# limitations).
Well, that and lacking writing/ideas for actual content. For instance I coded a basic adventure book reader (CYOA-type thing) but had no desire to actually write a story (so I didn’t develop it further).
*= I would not totally be against using GDscript (particularly as the language I want actually isn’t too different syntax-wise) particularly as I gain more experience, but I don’t think it would serve much of a benefit unless it was for a specific calculated reason. As in not my first-step or common use of time. Same with other languages, for instance something like a networking system could be done in any supported language thanks to how Godot handles languages. And that reason for a different language could just be what someone contributing to a project prefers.
So… my opinion regarding how I perceived C# and followed that statement up with it being subjective (aka, opinion), in your view, devalues the rest of my post. That’s your hang up?
It’s a single purpose language. Learning it will bring you no benefit other than using Godot.
Learn c# and you can do basicly anything you want.
Also gdscript is kinda ugly.
I disagree. Even if one is new to programming, learning GDScript still teaches one how to program. Loops, conditions, variables, functions… basically all that is programming is still part of GDScript and it would be no more difficult, once learned, to switch from GDScript to any other language as it would to switch from C#, C/C++, Python, etc. That is to say, once you understand how to program, it’s nowhere near as hard to switch languages as initially learning your first one.
That said, the same could be argued when working with different engines within the same language. C# in Unity, C# in Godot, and C# in ASP.Net applications all have their idiosyncracies that might make the language feel different, even though, at it’s core, it’s the same language. How a library functions can have a drastic effect on how you program a language, and if you change one library for another, even in the same language, you may find you have to alter your programming style.
Additionally, languages can be ported. GDScript currently only exists in Godot, but nothing is stopping anyone from writing a python-like or nodejs-like runtime interpreter for the language that allows you to use GDScript sans-Godot.
As for how nice the language looks… that’s subjective. I, honestly, find GDScript to be a very clean looking language (much like I do Python… probably unsurprisingly). C#, on the other hand, I find to be a verbose mess, seeming to take 100 lines of course to accomplish something I can do in 10 in other languages. But, again, that’s subjective
Personally, I like the idea of using bindings more than using GDscript* in Godot and my preferred language outside of Godot. From what I’ve seen, even if not perfect it’s much less likely to cause confusion having 1 workflow (+some extra context in Godot) rather than 2 (not just syntax, but also technical stuff). Also it’s nice to use code that doesn’t actually depend much on whatever engine/framework you happen to be using it in (particularly an imported file with procedures).
Though some of my perspective may be that I haven’t really used the language that I want to (mentioned in other comment) aside from a bit of tinkering with Raylib bindings (and a bit with Godot 3.X), so (aside from switching back-and-forth making less sense) I need Godot to learn the language just as much as I need the language to use Godot, all the things that motivate me (starting points for projects) are in various stages of viability particularly with how they relate to each other. Which admittedly is not the type of situation people wanting C# are in (…maybe some are with 4.X C# limitations).
Well, that and lacking writing/ideas for actual content. For instance I coded a basic adventure book reader (CYOA-type thing) but had no desire to actually write a story (so I didn’t develop it further).
*= I would not totally be against using GDscript (particularly as the language I want actually isn’t too different syntax-wise) particularly as I gain more experience, but I don’t think it would serve much of a benefit unless it was for a specific calculated reason. As in not my first-step or common use of time. Same with other languages, for instance something like a networking system could be done in any supported language thanks to how Godot handles languages. And that reason for a different language could just be what someone contributing to a project prefers.
That’s clearly vast exaggeration, and devalues the rest of your post.
So… my opinion regarding how I perceived C# and followed that statement up with it being subjective (aka, opinion), in your view, devalues the rest of my post. That’s your hang up?
Cool beans