gdnative

I'm not sure if you are referring to GDNative which is the native/binary "scripting" interface, or hacking on the engine code itself. Neither are the primary way to use Godot -- the documentation reflects that, I guess. A lot of the documentation is not language specific, and a lot of the topics covered are fundamental. The engine code is great. It's structured logically and navigating it is intuitive. Building the engine is simple, customisable, and documented well. Significant chunks of the engine are integrated as compiled in 'modules'. You can add your own modules and the build system lets you select which modules to include. Adding new node types and working with the scripting/binding system is pretty straight-forward. I think the documentation for working on the engine[0] and contributing to the project[1] (as well as the code itsel

I started working through this, except to make things difficult for myself I used Godot for drawing everything, via https://github.com/godot-rust/godot-rust. I only got to about halfway through section 2, but I think it was going well.

GDScript is essentially a slimmed-down Python with all the bad dev. experience stuff removed (version- & dependency management that is). Godot has C# support since 3.0[1]. Though to me C# seems as arbitrary as any language – Godot doesn't strive to compete with Unity. Why not use Scala or Lua? While I'm not a fan of Python I think its a reasonable choice given the target audience of devs using a game creation IDE/editor. Experienced devs who want to use the Godot ecosystem/frontend/engine can always use whatever to write their game in by adding the resp. bindings; e.g. Rust[2]. [1] https://docs.godotengine.org/en/stable/tutorials/scripting/c... [2] https://github.com/godot-rust/godot-rust