[frompdx]

I wouldn't get to hung up on GDScript. It works well and is well integrated into Godot. If you already have experience programming it will be easy to pick up. Where Godot shines is the ability to create something without a lot of code. This is a good thing because IMO the real time suck is creating assets.

[600frogs]

I suppose I'm coming at it from a different angle - I'm expecting my game to flop, but want to learn something from it. I'd rather that something learnt to include a "real" language rather than a script designed for one program. Of course, that's not to say I'll learn nothing while developing for Godot, but it is a factor for me.

[frompdx]

Well, you can use C# with mono or use GDNative. Personally, I think most are better off just using GDScript and focusing on their game. I say that because in r/godot there is always a lot of handwringing from newcomers who are wondering if they should skip ahead to something more advanced/common, but ultimately they want to make a game. If that's the case, I think GDScript is great. I think the real learning experience for any independent game developer is how to scope a project so that it is achievable with the resource constraints they have available. That's useful in all programming domains.

[krapp]

There are forks of Godot that use other languages[0].

You might still be able to learn algorithms and methods using Godot, but to me the primary reason to use a framework like Godot is to finish a game. You learn the framework to use the framework - the player isn't going to know or care either way.

[0]https://github.com/Vivraan/godot-lang-support