I think it's easy to get stuck in the mindset of "not knowing enough" to do the thing you actually want to do. There's always more to learn, especially with something as big as godot. You know several programming languages and different game frameworks - it seems like at this point you have a handle on most of the general game development techniques you need to achieve your goal. I think you should work on your game with the understanding that you will know more as you progress.
Games are such huge projects I think no matter how crystal clear your vision is of it is at the beginning there is guaranteed to be a large amount of iteration as you develop it. Know that there will be mistakes and failures and get to the more important job of iterating on your game design as fast as you can. Godot is very well suited to this task. You're definitely ready.
Interesting. I did the opposite: I put down Godot for Kaplay. Mostly because Godot is not made for the web. Specifically, the web builds are large: just using your Sonic Ring Run demo as an example, the JS version is about 5 MB, while the Godot version is 15 MB (*after* compression). For a mobile webgame It's not great for the engine binary alone to be more than a few megabytes. Anyway, we'll see if I have the same crippling performance issues that you had with Kaplay. I think every tool has problems, so the question is really which problems can you live with.
Been using Kaplay for my own project and have enjoyed the ease of programming with it (I too did web programming prior to being laid off). I've also already started to think beyond to other games I want to build/prototype in the future though and have wondered if it might already be time to start looking at Godot. It'd be a shame to leave Kaplay behind, but I don't know how well it'll be able to handle my ideas past a certain point.
I think it's easy to get stuck in the mindset of "not knowing enough" to do the thing you actually want to do. There's always more to learn, especially with something as big as godot. You know several programming languages and different game frameworks - it seems like at this point you have a handle on most of the general game development techniques you need to achieve your goal. I think you should work on your game with the understanding that you will know more as you progress.
Games are such huge projects I think no matter how crystal clear your vision is of it is at the beginning there is guaranteed to be a large amount of iteration as you develop it. Know that there will be mistakes and failures and get to the more important job of iterating on your game design as fast as you can. Godot is very well suited to this task. You're definitely ready.
If your output is the web, do take a look at Defold, should be better suited.
Interesting. I did the opposite: I put down Godot for Kaplay. Mostly because Godot is not made for the web. Specifically, the web builds are large: just using your Sonic Ring Run demo as an example, the JS version is about 5 MB, while the Godot version is 15 MB (*after* compression). For a mobile webgame It's not great for the engine binary alone to be more than a few megabytes. Anyway, we'll see if I have the same crippling performance issues that you had with Kaplay. I think every tool has problems, so the question is really which problems can you live with.
Been using Kaplay for my own project and have enjoyed the ease of programming with it (I too did web programming prior to being laid off). I've also already started to think beyond to other games I want to build/prototype in the future though and have wondered if it might already be time to start looking at Godot. It'd be a shame to leave Kaplay behind, but I don't know how well it'll be able to handle my ideas past a certain point.
Don't get attached to a tool if you can no longer achieve what you want to use it for. I think there's no harm in starting to learn Godot.