> My son had tried Unity first, but the C# compile cycle was so slow that he kept getting out of the flow.
I'd like to know more about this. Were you comparing similar sized projects? I've only done very small projects in Unity and the cycle was near instant. Loading up some of their 3gig+ samples, there was an initial build that took 40+ mins but that's because it had 3gig of assets to process.
It’s probably not compilation, but “Domain Reloading” (https://docs.unity3d.com/2022.2/Documentation/Manual/DomainR...) which is laughably slow and on by default.
I think Unity does this because the same process is re-used for Play and Editor modes, whereas Godot does the normal thing and spawns a new process when testing.
My entire experience with Unity is "my kid said it took long to run the game he was trying to make". Sorry that I can't be more helpful. He might've been unreasonably impatient, I never looked over his shoulder when he was trying out Unity. All I know is that he says he likes Godot way more, in no small part because it's "faster" (and I'm pretty sure he doesn't mean engine performance when he says "faster").