This rather dampened by enthusiasm for Godot: https://sampruden.github.io/posts/godot-is-not-the-new-unity...
It's carrying a lot of performance baggage and there seems to be no sense of urgency in fixing it.
It's carrying a lot of performance baggage and there seems to be no sense of urgency in fixing it.
Also IMO unless you want to share C++ plugins with others (via GDExtension), if you are making a game with it you'd want to modify the engine itself for any non-trivial functionality anyway. Again, the situation he describes sounds like it would be much better done by writing the reusable controller itself as a node written in C++ inside the engine itself (not via GDExtension) that uses the fast physics API directly.
Basically what he describes is an issue only in specific situations and not something that would really stop someone from making their game.
Personally, I found that signals were very slow for communicating node to node, was dropping information because it could take longer than a frame.