Interesting to learn that Unity devs use raycast function to detect collision. I imagine it would be much less of a problem with proper spatial partitioning ? But it would mean more work for the devs.
I'm not sure how Godot is handling raycasts under the hood vs Unity and if this is relevant to the performance difference, but I'd guess both would or should use spatial partitioning, and most would expect the engine to handle that. The dev could do it themselves if that was the bottleneck but yeah, more work. It may be though that it already is using decent spatial partitioning and the bottleneck is somewhere else.
Anyway on the general point about Godot's 'maturity' that's been talked about, Unity has had a ton invested into it, of course there'll be areas where Godot needs to improve or 'catch up'. But there's a better-than-ever chance now that Godot will be able to scale up development and optimization, via donations and more community feedback and involvement, patch submissions etc.
Of course Unreal is always a great option too, but for me at the moment, I think I'd like a lighter weight editor... I'm still plodding along on an old laptop, I can't do anything in Unreal unless I spin up and work off a cloud server. I think I am, sadly, done with Unity, even as a tinkerer.
blog.unity.com
