I get that. But again it's an endless stair of complexity and tool-building. So you can't write your game because first you need to improve your game engine! Bu

I get that. But again it's an endless stair of complexity and tool-building. So you can't write your game because first you need to improve your game engine! But your game engine needs improved graphics drivers, so you need to work on that! But graphics drivers only work well on a decent compositor, so you need to work on that! But a decent compositor needs a kernel architecture that actually does what it says on the tin, so you need to work on that! At what point do you say "enough!" and start writing the game not the tool? I say that for a kid starting out, that point is right at the start. IF they get good at games coding, THEN by all means get them interested in Godot and helping to write a new games engine. By then they'll have the understanding to be able to contribute.