Meanwhile, if you have more than 32 or so colors in a palette swatch, the color picker becomes permanently unusable for your project.

Godot is so driven by whatever sounds neat to work on that it has three completely different rendering systems, all buggy and mediocre. At least two shipped tilemap systems, one deprecated. And several systems like its autotiler where the community standard is to never use the built in one and to always replace it with a well known, much better add-on, and then to have to remember to avoid all the built in UI nudging you towards the built-in one.

Such a weird foundation for a project. Tons of hype but not a lot of successful games relative to usage.

I just love how Godot itself is under 100mb. Even as the project grows I hit play and it instantly loads.

Compared to Unity hitting flow state in Godot and sustaining it is trivial.

Godot is an easy choice for a Hackathon or a fun prototype project. And increasingly becoming my go to choice for larger projects.

I used to love Godot, then moved to WickedEngine. But AI is helping me replace it all.

For my games I manually worked through the Vulkan tutorial along with other essential components like input and sound.

Those austere code bases now act as constraints and frameworks for AI; the AI fills in the blanks for the specific game project.

I feed AI designs and it figures out the missing functionality.

Also have done similar to create my own scripting language; defined the compiler and grammar, syntax and have AI filling blanks.

These tight constraints have helped my local AI stay on rails. It can check Google Gemini when it's really stuck

Will leave the OS kernel and drivers up to those types. But I am well underway to an entire suite of userspace apps and my own Linux distribution that boots to my game engine as a "desktop" metaphor. Backed by a visual data model that can recreate the look of Firefox and renders websites as shaders