Bevy

一句话：技术上很优雅，但是 AI 最难写的引擎。

In one line: technically elegant, and the hardest engine for AI to write correctly.

⚠ 为什么对 AI 不友好

这一条是本站最强的判断，请认真对待：

Rust 的所有权模型对 AI 很不友好。

AI 写 Rust 时最常见的错误是借用检查失败：

```

cannot borrow x as mutable because it is also borrowed as immutable

```

⚠ 这类错误的成因是生命周期推断 —— 而 AI 没有真正的类型系统模型，

它只是在模仿训练数据里的代码形态。当代码需要跨越生命周期时，模仿就失效了。

这与 AI 写 Python/TypeScript 的差距是数量级的 —— 后两者里 AI 写的代码

即使风格不对也能跑，Rust 里直接编译失败。

⚠ Why it is unfriendly

This is the strongest judgement on this site; please take it seriously:

Rust's ownership model is very unfriendly to AI.

The most common error when AI writes Rust is a borrow-check failure:

```

cannot borrow x as mutable because it is also borrowed as immutable

```

⚠ These errors come from lifetime inference — and AI has no real model of a type system. It is imitating the *shape* of code it saw in training. When the code has to cross a lifetime boundary, the imitation breaks down.

The gap between this and Python/TypeScript is an order of magnitude — in those languages AI-written code usually runs even if the style is wrong. In Rust it simply fails to compile.

它值得的地方

⚠ 本站判断它技术方向是对的：

• 数据驱动 —— 组件 + 系统，逻辑与数据分离
• ECS 架构清晰 —— 比继承体系更好维护
• 开源彻底（Apache-2.0）—— 官方写「free and open-source forever」

Where it deserves credit

⚠ This site's judgement is that the technical direction is right:

• Data-driven — components plus systems, separating logic from data
• A clean ECS architecture — easier to maintain than an inheritance hierarchy
• Genuinely open (Apache-2.0) — the official line is "free and open-source forever"

如果你还是要用

⚠ 三个降低痛苦的做法：

1. 让 AI 写「一次性」的小系统，别让它写大的架构

2. 每次只改一处 —— 借用错误会连锁，改一处好定位

3. ⚠ 准备好花更多时间在编译错误上

If you still want to use it

⚠ Three ways to reduce the pain:

1. Have AI write small, throwaway systems rather than large architectural pieces

2. Change one place at a time — borrow errors cascade, and one change is easy to locate

3. ⚠ Budget more time for compile errors

什么时候选它 / 不选

选：⚠ 你本人是 Rust 开发者（那你根本不需要 AI 帮你写）

不选：单人 + 用 AI 做游戏 —— 这是本站最强烈的建议

When to pick it, and when not to

Pick it if: ⚠ you are a Rust developer yourself (in which case you do not need AI to write it)

Do not pick it if: you are solo and using AI — this is the site's strongest recommendation

可核验事实

Verifiable facts

术语

⚠ 「ECS」「数据驱动」这些词在 [Vibe Gaming 词条](../vibe-gaming.html) 里有解释。

Vocabulary

⚠ "ECS" and "data-driven" are explained in the [Vibe Gaming entry](../vibe-gaming.html).