如果你不是技术出身，却总在标题里看到诸如 “AI 一句话就能生成整部电影” 的新闻，或者刷到看起来像好莱坞的 demo 集锦——然后感觉脚下的地板在倾斜——我想让你知道的是：
如果你不是技术出身，却总在标题里看到诸如 “AI 一句话就能生成整部电影” 的新闻，或者刷到看起来像好莱坞的 demo 集锦——然后感觉脚下的地板在倾斜——我想让你知道的是：
你的恐慌，是按 demo 的刻度校准的，而不是按现实的刻度。它们不是一回事，而这条缝比标题党愿意承认的大得多。
我想用一个真实、具体的例子把这件事讲明白，因为那种抽象的安慰（“别担心，其实没那么先进”）人人都会说，但几乎从来不管用。
注
例子之前的一点说明。 我会拆解一个具体的开源项目，让这个模式变得具体可见，我会点名它。这不是对写它的实验室的攻击。我描述的这种模式——“精致的营销，包着半成品的代码”——现在几乎是病毒式传播的 AI 项目里的常态，而不是例外。普林斯顿大学的计算机科学家 Arvind Narayanan 和 Sayash Kapoor 甚至为这种模式取了一个“书本级”的名字（AI Snake Oil），他们认为这是行业性问题，而不是某个团队的单点失败。我要拿来举例的这个团队，其实做了非常有价值的事：他们交付了一份很有思想的架构草图，以及一些可用的集成代码，别人可以从中学习。问题不在他们；问题在于这类项目被呈现给大众的方式，与它们真实能做什么之间的落差。我之所以用它，是因为我刚好对它很熟。把这篇文章里出现的项目名替换成过去 18 个月里几乎任何一个“高 star 的 AI 项目”，大多数细节也仍然成立。
一个具体案例：看起来像未来的项目#
有一个开源项目叫 ViMax。它发布在 GitHub（软件发布的地方）。它有 6,500 个 “stars”（GitHub 版点赞）。它来自一个很受尊敬的大学实验室。它的 README（项目的门面页）声称：它可以把一句话的想法，比如 “一只猫和一只狗遇见一只新猫”，变成一部完整短片——角色一致、摄影专业、场景衔接顺畅、音频同步。页面上展示了一组精心打磨的演示视频网格：
一个非技术读者看到这些，很自然会得出结论：“AI 已经能拍完整电影了。电影人马上要被淘汰。我做的创意工作不再有意义。我孩子将来不会再有讲故事的职业。”
但如果你诚实地读一遍它的实际代码，你会看到的是：
- README 里最吸睛的那个所谓“质量检查（quality check）”功能——本应保证整部片子里角色一致——确实以文件的形式存在，但程序从来没有真正运行过它。 这就像汽车广告吹“安全气囊”，但车里根本没装。
- README 里标着 “Novel-to-Movie” 的整条流水线，甚至启动不了。 代码引用了项目里根本不存在的文件和文件夹，却被当成“可用”发布出来。
- 整个项目几乎没有质量测试。 程序生成一次图像，拿到什么就用什么；如果图错了，它不会察觉；下一步还会把错图当参照，错误一路叠加。坏掉的场景无法“重生成”，除非你手动删文件。
- README 里的 demo 是挑出来的。 你在任何地方都找不到一部真正由这个工具端到端、无人工干预生成并公开发布的片子。大概率是因为它很难稳定地产生“可看”的结果。
- 那 6,500 个 stars 反映的是：README 写得不错、demo 很吸引人、实验室名头够响。它们并不反映“有人用它做出了真实可用的作品”。给它点星的大多数人，甚至从没跑过代码。
这不是“门面宣称”和“真实能力”之间的一点小差距，而是一条鸿沟。
为什么这与你的焦虑有关#
类似的落差，现在几乎遍布整个 AI 行业。程度不一定都像这个例子一样夸张，但“这是规则而不是例外”：
- demo 往往是从很多次尝试里挑出来的最好结果。 你看到的那条“惊艳输出”，可能是从十次、一百次、甚至一千次尝试里人工挑出来的那一次。系统并不具备“你随手一用也能稳定得到同样输出”的能力。更隐蔽的是，连行业榜单也会发生同样的“挑样”：一篇对 LMArena 基准上 280 万次模型对比的分析（link）发现，选择性提交评测结果，会把公开分数最多抬高 100 分。
- 架构推介不是产品。 一张“AI 导演 → AI 编剧 → AI 摄影 → 成片”的流程图，描述的是愿景，不是工具。把每一个箭头都做成稳定可靠的现实产品，需要很多年，而大多数工作根本还没完成。2023 年最火、star 最多的 AI 项目 AutoGPT 就承诺过类似的“自动代理架构”；亚马逊研究者测量它完成一个基本购物任务的成功率只有 24%。到 2024 年 9 月，第二个最著名的例子 BabyAGI，甚至被它自己的作者归档（停止维护）了。
- “从想法到成片”是一句话的营销，不是一个可度量的指标。 没有人在测量“成片”到底是什么意思：质量门槛是什么？长度是多少？连贯性怎么定义？失败率是多少？“完整、成片、专业”这类词在这些宣称里承担了巨大的、无人监督的暗示工作。这个模式如今甚至已经能触发监管执法：自 2024 年 3 月起，美国证券交易委员会（SEC）开始以所谓 “AI washing” 为名，对公司“对投资者实质性夸大 AI 能力”的行为提起执法行动。监管机构不会为了偶发行为单独发明一个命名的执法项目。
- stars 和下载量是虚荣指标。 它们衡量的是注意力，而不是能力。一篇对 GitHub 仓库的学术分析（The Fault in Our Stars, NDSS MADWeb 2024）发现，一个项目的质量与 star 数之间没有统计显著的相关性；另有 2026 年来自 Carnegie Mellon、NC State 与 Socket 的研究，识别出在 18,617 个仓库里大约 600 万个疑似 fake stars 。这套指标不仅“相关性弱”，而且还会被主动操纵。一个工具可以有 50,000 个 stars 却根本不能用；一个工具也可以只有 200 个 stars 却 quietly excellent。数字告诉你的，是“炒作速度”，不是“功能价值”。
到这里为止，我讲的都是你从项目页面表面就能看到的信号：精选 demo、膨胀的 stars、描述愿望的架构图。但还有一个更深的信号，一旦你学会看它，你甚至不需要自己是工程师也能用得上。
这个信号是：底层代码有没有被认真照料。
真正耐用的软件——银行、医院、你上个月坐过的飞机上跑的那种软件——会像一家维护得很好的餐厅后厨一样，显露出“被照料”的痕迹，就算你不是厨师也看得出来。它会有 测试（tests）：一些小程序用来验证软件真的做到了它宣称的事。坏掉的功能会被 删除，而不是和“能用的部分”一起打包发布。错误会被认真处理，而不是一把扫进地毯底下。安装与配置说明会在陌生人的电脑上也能跑通，而不是只在作者自己的机器上成立。整个系统会自洽，而不是一层层半成品实验叠在更旧的半成品实验上面。
而在这个时代的大多数“病毒式 AI 项目”身上，你几乎看不到这些东西。还是以 ViMax 为例：
- 整个项目只有两份测试文件，而且都来自一个外部志愿者在同一个 PR 里的贡献——那个 PR 加的是另一个功能（对中国某 AI provider 的支持），测试也只覆盖了 那个 功能。更“糟糕”的地方在于：这两份测试其实写得不错——它们像一个合格示范，展示了这个代码库 本可以 怎么被测试。实验室合并了这份贡献，看到了“好测试长什么样”，然后仍然没有为项目里另外大约 25 个模块写类似测试。“没有测试”不是项目能力受限，而是作者在被示范过之后仍然做出的 选择。
- 项目里确实“附带”了一条叫 “Novel-to-Movie” 的流水线，但它完全不能工作。 它引用了项目里不存在的文件夹与文件。任何人只要试图运行它，都会立刻报错。这相当于餐厅菜单上写着厨房根本做不出来的菜。
- README 吹的那套“角色一致性检查（consistency check）”功能（代码文件在此）——本该确保整部片子里人物长相一致——写是写了，但从来没有被接入到真正运行的程序里。 这像一家医院建了急诊室，却忘了装门。
- 同一个操作被两套重试机制同时包了一遍，层层叠上去却没人注意到。本来该重试三次的东西，最终最多会重试到九次。这就是补丁一层层堆上去、却没人做清理时会出现的样子。
- 安装说明里把中国某大学的软件镜像硬编码成默认下载源：对写代码的那家实验室来说当然没问题；对世界上其他地方的人来说，要么失败，要么慢得离谱。团队里显然没有人站在“外人”的视角，从零开始装一遍。
评估这些根本不需要你懂编程。你只需要问一些非常朴素的问题：
- 这个项目有测试吗？
- 有没有“宣称有”的功能其实跑不起来？
- 门面上写的东西，真的被实现并连接起来了吗？
- 安装流程能在一个普通人的普通电脑上跑通吗？
- 有没有明显的死代码就躺在能运行的代码旁边？
一个项目只要在这些问题上频频失败——不管它有多少 stars、README 写得多 slick、哪个名校给它盖章——它都更像是一张 草图（sketch），而不是一个工具。草图很有价值：它展示想法，启发别人去做真正可用的版本。但你不应该把焦虑建立在草图之上，因为草图恰恰最容易在路演式叙事里被夸大。
这是你能掌握的最强单一信号，而且这也是 AI 炒作周期最努力想让你看不到的东西。营销页就是给人看的；代码不是。二者之间的不匹配——外表光鲜、内部靠胶带凑合——就是“AI 焦虑产业”滋生的主要空间。一旦你学会去“掀开引擎盖”（更现实的是：请一个值得信任的人替你看），恐慌的抓力会立刻掉下去大半。你会看见真正存在的东西是什么。
一个有用的类比#
现在的 AI demo，很多时候就是车展上的概念车。概念车开上舞台，长得像未来，带着你从没见过的特性：车灯会转向，车门像翅膀一样打开。
但你没被展示的是：
- 这辆车会被拖回后台。它其实没法可靠地在城市里开上一个街区。
- 它根本过不了任何安全检验。
- 量产版（如果它最终真的存在）至少还要五年，并且会砍掉 demo 里三分之二的特性。
- 很多概念车永远不会变成量产车。
当你看到一个 AI 视频 demo 时，你看到的就是概念车驶过舞台。你看的不是一个“任何人都能开回家”的工具。而这两者之间的距离，就是恐慌被制造出来的主要地方。
真实情况：把刻度调回现实#
把话说得更诚实一点：我当然也不可能反过来告诉你“AI 都是假的，别担心”。它不是假的。更诚实的图景是这样的：
今天确实已经成立的：
- AI 已经能从文本提示生成非常漂亮的 5–10 秒视频片段。三年前这还做不到；现在它是真的，而且有时惊艳。
- AI 正在被真正地融入创作流程里——用来打草稿、做分镜、生成素材、快速试想法。很多职业创作者用它来把既有工作做得更快，而不是“用它替换自己”。
- AI 正在以可感知的方式改变某些工作：图库摄影、某些插画工作、某些文案工作。它不是立刻替换掉 人，而是改变这些工作产出的形态与产出方式。
尽管 demo 看起来很像，但今天仍然不成立的：
- AI 仍然做不到：你只给一句提示，它就能按需生成一部连贯的长片、连贯的短片，甚至连贯的 90 秒叙事视频——且不需要大量人工干预与多次失败尝试。
- AI 并不以“讲故事所需的方式”理解故事、角色与受众。它是在超大规模文本与图像数据上做模式匹配——那是另一种东西。
- AI 并不处在一条平滑、必然的曲线之上，马上就会取代电影、音乐或写作。它更像一条 锯齿状 曲线：有些事会突然变得极其容易，而另一些事会顽固地难。判断哪些会变容易、哪些仍会难，比 demo 暗示的要难得多。
值得认真思考（但无需恐慌）的：
- 某些 容易自动化 的创意任务，其经济价值确实在下降。如果你的工作主要是生产那种 AI 现在 30 秒就能生成的东西——通用库存图、公式化营销文案、没有灵魂的解说视频——那么未来几年它的价值会被压缩。
- 判断力、品味、原创性与手艺 的经济价值，反而可能在上升——因为大量平庸的 AI 输出正在淹没渠道，人类筛选、人类打磨的作品会更显眼。
- 面对 AI 的正确反应，不是从创作里撤退，而是把更多投入放在 AI 做不好的部分：具体性、观点、真实体验、明确选择、真实风险。
如果你感到焦虑，可以怎么做#
- 自己上手试一试。 在 Runway、Pika、Sora 或任何面向消费者的 AI 视频工具上花 20 美元、20 分钟，你学到的会比看一百篇文章多。你会发现：AI 在某些方面确实比你想的更强；但在另一些方面又远比 demo 暗示的更受限。
- 看完整过程，而不只看结果。 看到 demo 时，问一句：他们没展示给我什么？ 试了多少次？人工挑选了多少？真实 prompt 是什么？用了多久？凡是他们没展示的部分，默认真相比高光剪辑更糟。
- 注意“宣称里缺失的词”。 “从想法到成片”并没有宣称：稳定地、达到某种 质量、任意 长度、不需要 人工帮助。那些被省略掉的词，才是它真正靠来成立的地方。
- 不要轻信圆整数字与 stars。 任何带着“病毒式指标”的东西，都被优化成更容易传播——而“容易传播”往往与“真实能力”几乎正交。
- 找一个刻度正常的人聊聊。 你身边如果有人真正在软件或 AI 行业里工作，一次 30 分钟的对话，可能就能帮你省掉几周焦虑。别找那些在社交媒体上 谈论 AI 的人——他们也有自己的激励结构。找真正“拿它在做东西”的人。
- 意识到：恐慌本身是一种产品。 末日叙事能带来点击、订阅与政治捐款；围绕你的 AI 焦虑形成的经济体系不是比喻。Future of Life Institute 被报道在一个数字媒体加速器里，以公开声明的 每月 10 万美元 的预算资助病毒式 AI 末日内容；一些 post-ChatGPT 的媒体分析记录了新闻报道向“危险框架”和耸动标题的可测量偏移；而末日派自己也组织严密、资源充足。卖给你的那一部分恐慌，有相当一部分是被人“有意制造出来”的，因为有人能从你的恐惧里获利。这并不意味着“什么都不会改变”——但这意味着：你的焦虑强度正在被人刻意向上拧，你不必接受这种拧动。
你在 demo 和标题里看到的那个 AI，并不是现实里存在的那个 AI。现实里存在的 AI：在一些狭窄方向上确实惊人，在很多宽广方向上仍然受限，而且在明年——或后年，甚至很可能再后年——都不会把人类创造力“整体淘汰”。
有些东西会变。有些工作会被重塑。有些行业会被压缩。自从织布机出现以来一直如此。但这不是同一件事，它不等于“你做的一切都不再重要”。
如果你只带走一句话：AI 的营销宣称与 AI 的真实能力之间的差距——在今天——比这项技术历史上的任何时候都更大。 你的恐慌是在回应营销。现实要混乱得多、推进得慢得多，也比营销希望你相信的更可控、更可导航。
你拥有的时间、主动权与相关性，都比头版标题告诉你的要多得多。
自己验证#
这篇文章里关于 ViMax 的具体指控，都对应到 GitHub 上可公开查看的文件。如果你想核验其中任何一条（或者项目在写作后有了变化），下面是按“它们支撑哪条主张”分组的直达链接。
项目本身
主张：所谓“quality check”功能作为文件存在，但从未接入运行程序。
主张：“Novel-to-Movie”流水线被发布出来，但无法运行。
主张：几乎没有测试；现有测试来自外部贡献者，而不是实验室。
主张：同一个操作被两套重试机制同时包了一遍。
主张：安装说明默认使用中国某大学的软件镜像。
以上所有链接均在 2026-05-21 进行了在线核验。若之后有移动或修改，项目主页 仍是权威入口，可从那里继续浏览内容。
延伸阅读#
如果你想看这篇文章里一些判断的研究来源——比如“精致营销包裹破碎代码”是行业性现象；基准测试常被游戏化；star 数被主动造假；恐慌本身是一门生意——下面按主题列出我认为最权威的材料。
关于 AI 炒作模式本身
关于机器学习的可复现性危机
关于基准测试游戏化与精选 demo
关于 GitHub stars：虚荣指标与造假
AutoGPT / BabyAGI 的警示案例
关于 SEC 对 “AI washing” 的执法
关于“被制造的 AI 恐慌”的经济学
以上延伸阅读链接同样在 2026-05-21 进行了在线核验。
A note to anyone feeling anxious about AI
If you're not technical, and you keep reading headlines about "AI generates entire films from one sentence" or watching demo reels that look like Hollywood — and feeling the floor tilt under you — here's what I'd want you to know.
Your panic is calibrated to the demos, not to the reality. They're not the same thing, and the gap is much wider than the headlines admit.
Let me explain this using a real, concrete example, because the abstract reassurance ("don't worry, it's not as advanced as it looks") is what people always say and it never lands.
NOTE
A note before the example. I'm going to walk through a specific open-source project to make the pattern concrete, and I'll name it. This is not an attack on the lab that wrote it. The pattern I'm describing — polished marketing wrapped around partly-finished code — is the rule across viral AI projects right now, not the exception. Princeton computer scientists Arvind Narayanan and Sayash Kapoor have a book-length name for this pattern — they call it AI snake oil, and they argue it's industry-wide rather than the failing of any single team. The lab whose project I'm using here did something genuinely valuable: they shipped a thoughtful architectural sketch and working integration code that others can learn from. The problem isn't them; the problem is the gap between how such projects are presented to the world and what they actually do. This project is simply the case I happen to know in detail. Replace its name throughout this article with nearly any other top-starred AI project of the last eighteen months, and most of the specifics would still apply.
A specific case: a project that looks like the future#
There's an open-source project called ViMax. It's posted on GitHub, the place where software is published. It has 6,500 "stars" — GitHub's version of a thumbs-up. It comes from a respected university lab. Its README — the front page of the project — claims it can take a one-line idea like "a cat and a dog meet a new cat" and produce a complete short film, with consistent characters, professional cinematography, scenes that flow together, and synchronized audio. The page shows a grid of polished demo videos:
A non-technical reader sees this and reasonably concludes: "AI can already make full movies. Filmmakers are about to be obsolete. My creative work doesn't matter anymore. My children won't have careers in storytelling."
Here is what an honest read of the actual code shows:
- The headline "quality check" feature — the part that's supposed to make sure characters look consistent across the film — exists as a file in the project but is never actually run. It's like a car ad that brags about airbags, when the airbags aren't installed.
- A whole pipeline labeled "Novel-to-Movie" in the README won't even start. The code refers to files and folders that don't exist in the project. It's been shipped as if it works.
- There are no quality tests anywhere. The program generates an image once, takes whatever comes back, and uses it. If the image is wrong, the program doesn't notice. The next step uses the wrong image as its reference and the error compounds. A bad scene cannot be regenerated except by manually deleting files.
- The demos in the README were cherry-picked. No film made with this tool, end-to-end, with no human intervention, is published anywhere. Probably because they don't reliably come out watchable.
- The 6,500 stars reflect that the README is well-written, the demo reel is compelling, and the lab name is recognizable. They do not reflect that anyone has used this tool to make something real. Most of the people who starred it never ran the code.
This is not a small gap between "what the front page claims" and "what the technology actually does." It's a chasm.
Why this matters for your anxiety#
The same gap exists across the AI industry right now. Not always to the same degree, but it's the rule, not the exception:
- Demos are best-of-many. When you see an AI demo, you are seeing the one good output from ten or a hundred or a thousand attempts, often with a human curating which one to show you. The system is not capable of producing that output on demand for you. The cherry-picking happens even at the level of which model versions get evaluated on industry leaderboards: an analysis of 2.8 million model comparisons on the LMArena benchmark found that selective submissions inflated published scores by up to 100 points.
- Architecture pitches are not products. A diagram showing "AI Director → AI Screenwriter → AI Cinematographer → Finished Movie" describes an aspiration, not a tool. Building each of those arrows reliably is the work of years and is mostly not done. The most-starred AI project of 2023, AutoGPT, promised exactly this kind of autonomous-agent architecture; Amazon researchers measured it completing a basic shopping task 24% of the time. By September 2024, BabyAGI — the second most-famous example — had been archived by its own author.
- "From idea to finished video" is a marketing sentence, not a measurement. Nobody is measuring what "finished" means, what quality bar, what length, what coherence, what failure rate. Words like "complete," "finished," "professional" are doing enormous unsupervised work in these claims. This pattern is now legally actionable: since March 2024 the U.S. Securities and Exchange Commission has been bringing enforcement cases against companies for what it calls "AI washing" — materially overstating AI capabilities to investors. Regulators don't invent named enforcement programs for one-off conduct.
- Stars and download counts are vanity metrics. They measure attention, not capability. An academic analysis of GitHub repositories (The Fault in Our Stars, NDSS MADWeb 2024) found no statistically significant correlation between a project's quality and its star count, and a 2026 study from Carnegie Mellon, NC State, and Socket identified roughly six million suspected fake stars across 18,617 repositories. The metric is not just weakly correlated with quality — it's actively gamed. A tool can have 50,000 stars and not work; a tool can be quietly excellent with 200 stars. The number tells you about hype velocity, not functional value.
Everything I've described so far — the curated demos, the inflated star counts, the architectural diagrams that describe wishes — those are tells you can spot on the surface of a project's web page. But there's a deeper tell, and once you know what to look for, you can use it without being a software engineer yourself.
The tell is whether the underlying code is cared for.
Real, durable software — the kind that runs banks, hospitals, the airplane you flew last month — has visible signs of care, the same way a well-maintained restaurant kitchen has signs of care even if you're not a chef. There are tests — small programs that verify the software actually does what it claims. Broken features are deleted, not shipped alongside working ones. Errors are handled deliberately, not swept under a rug. The setup instructions work on a stranger's computer, not just on the original author's. The whole thing is consistent with itself, not a layer of half-finished experiments piled on top of older half-finished experiments.
Most viral AI projects of this era fail nearly all of these tests. Using ViMax again, since it's the case we already opened up:
- The entire project contains two test files, both contributed by an outside volunteer in a single pull request that added a different feature (support for a Chinese AI provider), and the tests only cover that feature. Here's the part that makes it worse, not better: the two test files are actually well-written — a competent worked example of how this codebase could be tested. The lab merged the contribution, saw what good testing of their own code looks like, and then wrote no similar tests for any of the project's other roughly twenty-five modules. The absence of testing isn't a limitation of the project — it's a choice the project's authors kept making after being shown an alternative.
- A whole pipeline called "Novel-to-Movie" is shipped as part of the project but doesn't function at all. It references files and folders that don't exist in the project. Anyone who tried to run it would get an immediate error. This is the software equivalent of a restaurant menu listing dishes the kitchen can't make.
- The headline "consistency check" feature — the one the README brags about, the part that's supposed to make sure characters look the same across the whole film — was written, but was never connected to the program that actually runs. It's a hospital that built an emergency room and then forgot to install the doors.
- The same operation is wrapped in two retry systems at once, layered without anyone noticing. What should retry three times retries up to nine. This is what happens when patches are stacked over months and nobody cleans up.
- The install instructions hard-code a Chinese university's software mirror as the default download source, which works fine for the lab that wrote it and fails or runs glacially slow for everyone else in the world. Nobody on the team tried installing it from scratch as an outsider would.
None of this requires programming knowledge to evaluate. You can ask plain questions:
- Does the project have tests?
- Are there shipped features that don't actually work?
- Is what's claimed on the front page actually built and connected?
- Does the install procedure work for a stranger on a normal computer?
- Is there obvious dead code lying next to working code?
A project that fails those questions is, regardless of how many stars it has, how slick its README looks, or which university stamped it — a sketch, not a tool. Sketches are valuable. They demonstrate ideas. They inspire other people to build the real version. But a sketch is not what you should base your anxiety on, because a sketch is exactly the kind of thing whose pitch deck wildly overstates its capability.
This is the strongest single tell you have, and it's the one the AI hype cycle works hardest to keep out of view. Marketing pages are designed to be looked at. Code is not. The mismatch between the two — the polished front, the held-together-with-tape inside — is where most of the AI-anxiety industry lives. Once you've learned to look under the hood (or, more realistically, to ask someone trustworthy to do it for you), the panic loses most of its grip. You can see what's actually there.
A useful analogy#
AI demos right now are concept cars at an auto show. The concept car drives onto the stage. It looks like the future. It has features you've never seen. The headlights swivel. The doors open like wings.
What you are not shown:
- The car is towed back off the stage. It cannot actually drive a city block reliably.
- It would not pass any safety inspection.
- The production version, if it ever exists, will be five years away and will lack two-thirds of the demoed features.
- Many concept cars never become production cars at all.
When you see an AI video demo, you are watching the concept car cross the stage. You are not watching a tool that anyone can drive home. The gap between those two things is where most of the panic is being generated.
What's actually true, calibrated#
It would be dishonest to swing the other way and tell you "AI is fake, don't worry." It isn't fake. Here's a more honest picture:
Genuinely true today:
- AI can generate beautiful 5-to-10-second video clips from a text prompt. This was impossible three years ago. It is now real, and the clips can be stunning.
- AI is being usefully integrated into real creative workflows — as a sketching tool, a storyboarding aid, an asset generator, a way to test ideas quickly. Working creatives are using it to do their existing work faster, not to replace themselves.
- AI is changing some kinds of jobs in concrete ways — stock photography, certain illustration work, some kinds of copywriting. Not by replacing the people in those fields immediately, but by changing what they produce and how.
Not true today, despite the demos:
- AI cannot, on demand, generate a coherent feature film, or a coherent short film, or even a coherent 90-second narrative video, from a single prompt, without extensive human intervention and many failed attempts.
- AI does not "understand" stories, characters, or audiences in the way storytelling requires. It pattern-matches across very large amounts of text and image data, which is a different thing.
- AI is not on a smooth, inevitable curve to replacing filmmaking, music, or writing. It's on a spiky curve where some things get dramatically easier and other things stay stubbornly hard, and predicting which is which is much harder than the demos suggest.
Worth thinking carefully about (but not panicking over):
- The economic value of certain easily automatable creative tasks is genuinely dropping. If your work consists of producing the kind of output that AI now produces in 30 seconds — generic stock imagery, formulaic marketing copy, soulless explainer videos — that work is going to compress in value over the next few years.
- The economic value of judgment, taste, originality, and craft is, if anything, increasing — because so much mediocre AI output is flooding the channels that human-curated, human-crafted work stands out more.
- The right response to AI is not to retreat from creative work but to invest more in the parts of it that AI is bad at: specificity, point of view, lived experience, deliberate choice, real risk.
What to do if you're anxious#
- Try the tools yourself. Twenty dollars and twenty minutes on Runway, Pika, Sora, or any consumer AI video tool will teach you more than a hundred articles. You will discover both that AI is more capable than you feared in some ways, and far more limited than the demos suggested in others.
- Watch the full process, not just the output. When you see a demo, ask: what didn't they show me? How many attempts? How much hand-curation? What was the prompt actually? How long did it take? Anything they didn't show you, assume the truth is worse than the highlight reel.
- Notice what's missing from claims. "From idea to finished video" doesn't claim reliably, at quality, of any length, without human help. Those omissions are doing all the work.
- Distrust round numbers and stars. Anything with viral metrics has been optimized for virality, which is mostly orthogonal to capability.
- Find someone calibrated. A friend who actually works in software or in AI can save you weeks of panic in a 30-minute conversation. Not someone who talks about AI on social media — those people have their own incentives. Someone who builds with it.
- Recognize the panic itself is a product. Doomsday framings drive clicks and subscriptions and political donations, and the economy around your AI anxiety isn't metaphorical: the Future of Life Institute has been funding viral AI-doom content at a stated $100,000 per month through a digital-media accelerator, post-ChatGPT media analyses document a measurable shift in news coverage toward danger framing and sensational headlines, and the doomers themselves are organized and well-resourced. Some of the panic being sold to you is being manufactured, deliberately, by people who profit from your fear. That doesn't mean nothing is changing — but it means the intensity of your anxiety is being deliberately tuned upward, and you don't have to accept that tuning.
The bottom line#
The version of AI you see in the demos and the headlines is not the version that exists. The version that exists is genuinely impressive in narrow ways, genuinely limited in wide ways, and genuinely not about to render human creativity obsolete next year — or the year after, or probably the year after that.
Some things will change. Some jobs will reshape. Some industries will compress. That's been true since the loom. It is not the same as "everything you do no longer matters."
If you take one thing from this: the gap between what AI is marketed as doing and what AI actually does is, right now, larger than at any point in the technology's history. Your panic is responding to the marketing. Reality is much messier, much slower, and much more navigable than the marketing wants you to believe.
You have more time, more agency, and more relevance than the front pages are telling you.
Verify for yourself#
The specific claims about ViMax in this article all point to publicly viewable files on GitHub. If you'd like to confirm any of them — or if the project has changed since this was written — here are the direct links, grouped by which claim each one backs.
The project itself
Claim: the "quality check" feature exists as a file but is never connected to the running program.
Claim: the "Novel-to-Movie" pipeline is shipped but doesn't function.
- The file: https://github.com/HKUDS/ViMax/blob/main/pipelines/novel2movie_pipeline.py
- How to verify: read the very first line —
# TODO: NOT IMPLEMENTED YET — and look at the imports at the top. It imports from components.event import Event and from pipelines.base import BasePipeline. Then look at the repository's file list: there is no components/ folder and no pipelines/base.py. The pipeline cannot start.
Claim: there are essentially no tests, and the tests that exist are there because of an outside contributor — not the lab.
- The tests folder: https://github.com/HKUDS/ViMax/tree/main/tests
- The pull request the tests arrived in: https://github.com/HKUDS/ViMax/pull/36 (MiniMax provider support, by an external contributor — note that the tests are tied to that feature, not to the project's video-generation pipeline)
- How to verify: count the files in the tests folder — two, both about a feature unrelated to video generation. Then read them: they're actually well-written. That's the most damning detail, not a redeeming one. The lab was shown exactly what good testing of this codebase looks like, merged the contribution, and then did not write similar tests for any of the project's other modules. The absence of testing is a choice, not a constraint.
Claim: the same operation is wrapped in two retry systems at once.
Claim: the install instructions default to a Chinese university's software mirror.
All links verified live on 2026-05-21. If any have moved or been changed since, the main repository page remains the canonical entry point and the contents can be browsed from there.
Further reading#
If you'd like the research behind the claims in this article — that the polished-marketing-around-broken-code pattern is industry-wide, that benchmarks are routinely gamed, that star counts are actively faked, that the panic itself is a funded industry — here are the most authoritative sources, grouped by topic.
On the AI hype pattern itself
On the reproducibility crisis in machine learning
On benchmark gaming and cherry-picked demos
On GitHub stars as vanity / faked metrics
The AutoGPT / BabyAGI cautionary tale
- AutoGPT Got 100K Stars and Then What? — retrospective on the most-starred AI project of 2023, including the 24% shopping-task success rate and BabyAGI's September-2024 archival by its own author.
On SEC "AI washing" enforcement
On the economy of manufactured AI panic
Further-reading links also verified live on 2026-05-21.