if you're lame and stinky, maybe.

I am probably going to get downvoted, but Godot isn't a replacement for UE (yet). It can be used if one is a solo dev, or can be used to replace Unity.

I have used Godot and am using UE almost daily, I have also used some assets in the video. 70 FPS for those low poly assets on a tiny map, running on RTX 5080 isn't good, quite the opposite. I'll get much better result in UE using the exact same assets. The video doesn't talk much about UE.

Most assets are made with UE/Unity in mind. So they'll 'look good' if you just import into those engines. Every engine uses a different way of setting up lighting, refelctions, shadows. If I directly import a UE asset into Godot, it will look bad because I have to setup lighting for it.

Someone made a comparison of reflections in Godot and UE on discord. Reflections look wrong in Godot when you compare that to UE. Godot is getting better, but it's not quite there yet. In O3DE's (another foss game engine, but slop) discord, someone vibecoded its renderer Atom, into Godot, and even that slop had better reflections.

Also the reason people use UE is not just good lighting/flash, it's things like Blueprint, Gameplay Abilities system, accessible facial mocap, GASP, templates and other systems already implemented for you. All of these are not primary focus in a general use engine like Godot/Unity. I need to use a separate plugin for terrain scultping in Godot. I know devs (mostly designers) who use UE just because of the Blueprint visual scripting.

What I don't get is, there are other small open source engines that have much better 'defaults'. Maybe it's the Godot Foundation's way of having everything done differently. Or maybe they can't do a breaking change when they are supporting really old hardware too.

I don't think games made with Godot look bad, quite the oppsite if people look at devlogs or posts shared by devs on socials. It is really great for the PSX style games.

At this point, I'm just waiting for the day when I'll try to initiate a conversation with a meat-drone, and instead of asking ChatGPT what opinion they're supposed to have about what I'm saying to them, they'll completely surrender the last vestiges of their shredded cognitive capabilities and just hold out their phone so I can chat with their LLM directly and leave them out of it. Probably while drooling a bit.

Make it fun!

It’s 2026, if you can’t effectively multi-thread and learn to parallelize processes i question your effectiveness as a dev.

Especially when you're architecting an engine targeting AAA development which needs to eek out every spec of performance they can. Like this isn't them forgetting to use a feature of a language, this is them just not even adding it.

The LLVM also seems like a poor choice. Sure it'll be fine for many but it's still adding overhead and will make it harder to optimize that last 5% to nudge into okay performance. Hardware isn't constantly evolving and being upgraded at the pace it used to.

And actually go look at the syntax of Verse. It's painful to read, which explains why they're pushing LLM driven development so they don't have to see their own monster

It's for gameplay programming, not engine subsystems. These events must eventually be serialized (in the serializability sense, not marshaling) and handled by a single thread for the net code to work. Basically every engine does this (or risk having unreliable networking). The goal of this (last time I looked was when it was announced) is to make it easier to have distributed networking for multiplayer games.

Also building this using c++ and LLVM will result in better performance than any blueprint system can achieve.

We can hate AI and the direction of the engine but don't just assume the devs at Epic are dumb.

Fun fact, someone tried to vibe up something at my work and it totally screwed up threading...

Maybe that's why epic can't do multi thread...

Are you referring to the suggestion to use AI to migrate old projects?