This isn’t a “Unity betrayed me” post. I’m Not Quitting Unity — I’m Relearning Game Development!

I still use Unity. I respect what it does well. It ships games. But I reached a point where I realized something uncomfortable:

I was getting good at Unity… but not necessarily at game development…?

So instead of quitting Unity, I stepped sideways — into Rust, Bevy, and game frameworks!

Engines make you productive — frameworks make you honest

Unity is incredible at momentum. You drag components, tweak values, press Play, and something works. That’s not a criticism — that’s why it’s popular.

But it also means a lot of decisions are already made for you.

When I started experimenting with Bevy, that safety net disappeared fast. No editor magic. No “just add a component and see.” You write systems. You define data. You decide how things actually flow.

At first, it’s uncomfortable. Then it’s addicting!

Frameworks don’t ask “what engine feature do you want?” — They ask “how should this game actually work?”

Bevy and Rust don’t care about your feelings

Enter Bevy. And Rust.

No inspector. No magic. No “it just works” hand-holding.

At first, it’s brutal.

Rust forces you to be explicit. Bevy forces you to structure your thoughts.

You don’t hope something updates — you schedule it. You don’t assume data is safe — you prove it.

No editor tricks. No lifecycle magic. Just data in, data out.

Once you write this, ECS stops being “confusing” forever!

Frameworks expose the lie engines sell

Engines sell you a comforting idea:

“Don’t worry about how games work — we’ve got it.”

Frameworks respond with:

“No, actually, you should worry about that.”

And they’re right.

Learning a framework:

• breaks your dependency on editor workflows
• forces you to design systems instead of stacking behaviors
• reveals which problems are yours versus engine-imposed
• makes every other engine easier, not harder

After writing real systems in Bevy, Unity feels… smaller. Not worse. Just less mysterious.

This isn’t burnout — it’s deprogramming

People assume exploring frameworks means you’re burned out or angry.

I’m neither.

I’m just tired of:

• being locked into one mental model
• confusing productivity with understanding
• treating engines like they’re the skill

Unity is a tool. Godot is a tool. Unreal is a tool.

Game development is the skill. And skills don’t come from hiding complexity — they come from facing it!

The takeaway

If an engine switch scares you, you’re probably too dependent on the engine.

Frameworks don’t make you slower in the long run — they make you harder to replace, harder to lock in, and harder to bullshit.

I’ll still use Unity. But I don’t want Unity living rent-free in my brain anymore.

Learning Rust and Bevy isn’t about rebellion. It’s about ownership.

And once you feel that, it’s very hard to go back.