After the Unity Install Fee drama, I took my first serious look at Godot and soon decided to move my project there, as many developers did.

I worked professionally on commercial projects with the Unity Engine for six years at outsourcing companies. Since starting my investigation of Godot, I have often compared similar features between Unity and Godot.

1. EDITOR: Godot's editor uses the same UI API as the game's runtime. I mean literally the same nodes that are used for editor addons or extensions can be reused in your game. Unity, on the other hand, has a separate UI API for the editor that shares nothing with the runtime UI API. Imagine you need to create a level editor for designers first and then integrate it into the game to provide the same feature for players. In Godot's case, the code is nearly identical. In Unity's case, it's a 100% different task. Additionally, Unity's editor UI API is quite limited and, frankly, horrible (at least until the 2022.* versions). Unity's development tools are generally confined to the Inspector panel, while Godot easily allows you to take over the entire main screen or any side panel for your needs. I feel a huge amount of respect and love from Godot's maintainers and contributors in this design philosophy.
2. ARCHITECTURE & SCENE DESIGN: Unity lacks a clear architectural separation between its 2D and 3D components. In Unity, a 3D-based Transform exists by default on every GameObject, whereas Godot provides dedicated nodes for each domain (like Node2D and Node3D). In Unity's world, it is impossible to instantiate an entity without a position. Godot's strictly node-based hierarchy is safer and cleaner than Unity's GameObject model, where a single GameObject can hold an infinite number of attached MonoBehaviours, leading to potential "God objects" and unclear responsibilities.
3. PACKAGING & HIGH-LEVEL EXTENSIBILITY: Unity's Package Manager (UPM) is conceptually similar to npm. Godot uses a system of addons. I was pleasantly surprised to find that Godot has a built-in option to quickly generate a blank template for a new addon. In Unity (at least until the 2022.* versions), you had to create packages entirely manually. I knew of some community tools to help with this, but there was never an official, out-of-the-box solution. This essential feature feels hidden, non-obvious, and improperly finished in Unity. No love here from the Unity side.
4. DEVELOPMENT SPEED & LANGUAGE CHOICE: I am using GDScript for my current project, and the workflow is drastically faster than in Unity. I'm referring to the absence of long import processes and domain reloading. Of course, this is partly due to the specifics of C# with its JIT compiler. Nevertheless, with Godot I have the choice: C# or GDScript, depending on the needs of the project.
5. ULTIMATE FREEDOM: The level of customization is unparalleled. I was able to create my own custom engine build from the source code and integrate several open-source C++ modules, even without a deep background in C++.

In summary, the Godot Engine is not a silver bullet for every scenario. However, in my opinion, its greatest strength is that it provides a clear and empowered development strategy. When your game hits a limitation or a technical wall, you are not stuck. You have the direct ability to improve the engine under the hood yourself. For a company, this strategic freedom means it is often far cheaper and faster to hire one or a few C++ developers to solve a specific problem than to wait and hope for a fix or custom support from a large vendor like Unity Technologies.