✦   ✦   ✦

breaking news

News, read through The Primal Race
← 全部评论 · all commentary

被裁掉的人不算资产The Laid-Off Aren't Assets

文娱 结构层 · 文化层 Polygon.com ↗ 2026-11-01 § 链接
新闻摘要《毁灭战士》创作者John Romero确认,其工作室去年被Xbox取消的项目已找到新发行商,得以继续开发。工作室最初从110人缩减至5人,截至2026年10月约有15名开发者,游戏已按小团队规模重新设计。
The newsDoom creator John Romero confirmed that his studio's project, canceled by Xbox last year, has found a new publisher. The studio shrank from 110 developers to 5, and as of October 2026 employs about 15; the game has been redesigned for the smaller team.
110人砍到5人,救回来的不是那105个
110 down to 5. What got saved wasn't the 105.

一条游戏行业的新闻,读起来像励志故事:Xbox 2025 年大裁员时砍掉了 Romero Games 的 AAA 项目,工作室从 110 人缩到 5 人,一年多以后 John Romero 靠一个熟人关系找到了新发行商,把项目救回来了。报道的语气是庆幸的——「很高兴看到原项目的一部分能重见天日」。但被救回来的是 IP、是美术、是代码资产,是「角色可以搬过来」「射击游戏有很多通用代码」。人不在这个清单里。

Romero 说他把一些被裁的开发者重新雇了回来。截至 2026 年 10 月,工作室大约 15 人。110 到 15,中间那 95 个人没有下文。报道没写他们去了哪里,这不是报道的失职,是这件事本身的结构:在「项目能否存活」的叙事里,开发者是可替换的零件,项目才是主体。裁员发生时他们是成本,项目复活时他们是「被重新雇用的一些人」。从头到尾没有人问过,那 95 个人这一年多靠什么活着。

这里动的不是直接暴力,是结构层。Xbox 的大规模裁员不是某个人拍脑袋的恶意,是资本在季度报表上的资源重新分配,而分配的结果是:风险向下转移,收益向上归集。母公司砍掉项目,成本由 110 个具体的人承担;项目被救活,功劳记在创始人和新发行商头上。Romero 能救回项目,靠的是他本人的行业人脉——「我联系了一个我认识的人」——这恰恰说明,在这种结构里,能活下来的不是项目质量,是创始人手里有没有那条线。没有这条线的工作室,报道最后一句已经说了:「其他受到类似影响的团队就没这么幸运了。」

再往上一层看,这条新闻被写成好消息,本身就是一次叙事操作。它把一次结构性裁员包装成一个关于坚持和转机的故事,读者的情绪被引向「太好了,游戏能玩到了」,而不是「为什么 110 个人的生计可以由一次财报决定」。这不是说 Romero 不该救自己的项目——他当然该救——而是说,当「项目复活」成为唯一的胜利叙事时,被裁掉的人就自动从故事里消失了,连消失都不算损失,因为故事从一开始就没把他们算进去。

真正值得追问的是:如果这条新闻消失,什么差额会变大?项目会消失,玩家少一个游戏,这算损失。但那 95 个人的处境不会因为这条新闻变好或变坏,他们从来不在这个等式里。一条把「15 人」写成好消息的报道,等于在说 95 个人的消失是这场复活可以接受的成本。这不是 Romero 一个人的问题,是整个行业默认的记账方式——人被记在支出栏,项目被记在资产栏,而资产可以搬家,人不行。

This reads like a comeback story: Xbox killed Romero Games' AAA project in its 2025 mass layoffs, the studio shrank from 110 developers to 5, and over a year later John Romero found a new publisher through a contact he knew. The tone is relief — good to see part of the original project survive. But what survived is IP, art, code assets, "characters we can move over," "shooters have a lot of common code." People are not on that list.

Romero says he rehired some of the developers he had to lay off. As of October 2026 the studio employs around 15. From 110 to 15, the other 95 have no epilogue. The report doesn't say where they went. That's not a failure of the report; it's the structure of the thing. In the narrative of "will the project live," developers are replaceable parts and the project is the subject. During the layoffs they were costs. When the project revived they became "some of the developers" who got rehired. Nobody, at any point, asks how those 95 people lived for the past year.

What moves here isn't direct violence. It's structural. Xbox's mass layoffs weren't one person's malice; they were capital reallocating resources on a quarterly report, and the result is risk pushed downward, credit pulled upward. The parent company kills the project, and 110 specific people absorb the cost. The project gets saved, and the founder and the new publisher get the story. Romero saved it through personal industry connections — "I just contacted somebody that I knew" — which tells you exactly what decides survival in this structure: not the quality of the project, but whether the founder has that line. Studios without the line get the last sentence of the article: other teams affected the same way "haven't been as lucky."

One layer up, the fact that this is written as good news is itself the operation. A structural layoff gets repackaged as a story about persistence and turnaround, and the reader's feeling is routed toward "great, the game will exist" rather than "why can 110 livelihoods be decided by one earnings report." This isn't a knock on Romero for saving his project — of course he should. It's that when "the project survives" becomes the only victory narrative, the laid-off automatically drop out of the story, and their dropping out isn't even counted as a loss, because the story never counted them in.

The real question: if this article vanished, what gap would widen? The project would vanish, players would lose a game — that's a loss. But the situation of those 95 people wouldn't change either way. They were never in the equation. An article that frames "15 developers" as the good news is saying, quietly, that the disappearance of 95 is an acceptable cost of this revival. That's not Romero's problem alone. It's the industry's default bookkeeping: people go in the expense column, projects go in the asset column, and assets can move. People can't.