Beginning of the Ende (a community Deno fork)

Document: WM-105 P. Webb Category: Tooling 2026-10-11 Beginning of the Ende Abstract The trend of VC-backed tooling ending in abandonment rears its ugly head again. But hey, people gotta eat, right? The community will pick up the slack and steward the projects, right?

文档：WM-105 P. Webb 分类：工具 2026-10-11 Ende 的开端摘要：风险投资支持的工具最终被抛弃的趋势再次抬头。但嘿，人总得吃饭，对吧？社区会接手并管理这些项目，对吧？

Body Deno is dead. Announced[1] on a Friday[2], of course, the team has fled to Cloudflare and in a year, will stop working on the runtime. Kudos to them for finding an exit, Womp womp to us. This is the second time in just as many years that a technology I depend on is “given up to the community.”

正文：Deno 死了。不出所料，团队在周五宣布[1][2]他们已经投奔 Cloudflare，并将在一年内停止对该运行时的开发。祝贺他们找到了出路，我们则只能自认倒霉。这是我在短短几年内第二次遇到我所依赖的技术被“交给社区”。

If you’re new here, Disc[3] came about because the team behind Gel fled to Vercel and gave their project up to the community. This was two years ago and as of this writing, no updates have been made on the “blessed” fork[4] of it. (Perhaps a bit petty of me to point out but someone in the Gel Discord has been rather hostile/cowardly about my efforts and thus I find delight in proving assholes wrong)

如果你是新来的，Disc[3] 的出现是因为 Gel 背后的团队投奔了 Vercel，并将他们的项目交给了社区。那是两年前的事了，截至本文撰写时，该项目的“官方”分支[4]没有任何更新。（指出这一点可能显得我有点小气，但 Gel Discord 里有人对我的努力表现得相当敌对/懦弱，所以我很高兴能证明这些混蛋是错的。）

The frustration of the Deno community is palpable and has created the best crashout[5] I’ve seen in some time: What the fuck do you mean Deno is ending development in a year???? I JUST learned how to use this stupid runtime. I don’t give a fuck about your Cloudflare acquisition or your edge computing or whatever the fuck a Durable Object is. I JUST WANT TO RUN MY TYPESCRIPT FILES. Why is there a shutdown date???? WHERE IS THE FUCKING DOWNLOAD BUTTON FOR MORE YEARS OF SUPPORT????

Deno 社区的沮丧情绪显而易见，并引发了我近期见过的最精彩的崩溃[5]：“你他妈是什么意思，Deno 一年后要停止开发了？？？？我才刚学会怎么用这个蠢运行时。我才不在乎你们的 Cloudflare 收购案，也不在乎你们的边缘计算，或者什么他妈的 Durable Object。我只想运行我的 TypeScript 文件。为什么会有停用日期？？？？更多年支持的下载按钮他妈的在哪里？？？？

I went to the releases page and there is no deno-forever.exe. WHY IS THERE NO deno-forever.exe????? Just compile another 10 years of development into a fucking executable and give it to me. I don’t want to learn Node.js again. I don’t want to migrate to Bun. I don’t want to understand your business model. I JUST WANT MY DINOSAUR BACK. You cannot just Deno.exit(0) an entire runtime. STUPID FUCKING CLOUD NERDS.

我去了发布页面，根本没有 deno-forever.exe。为什么没有 deno-forever.exe？？？？把未来 10 年的开发成果编译成一个他妈的可执行文件给我不就行了吗。我不想再学 Node.js 了。我不想迁移到 Bun。我不想理解你们的商业模式。我只想找回我的恐龙。你们不能就这样 Deno.exit(0) 掉整个运行时。你们这群愚蠢的云端书呆子。

Ryan Dahl’s comment[6] on HackerNews gave me pause (emphasis mine): It’s a joint decision and I agree with it. I’m most invested in its success and have put the most work into it - and I no longer think it’s where I can do the most important work. There are some good ideas in Deno and it’s well engineered - but it ultimately is not solving big problems. It has been sucked into the gravity well of node compatibility, which forces it to behave exactly as Node does. Why reimplement Node? It works. Marginal performance or UX or security benefits are not enough. … We’ll ship monthly releases for a year, and Deno stays MIT-licensed. If people want to carry it forward, I’d like that.

Ryan Dahl 在 HackerNews 上的评论[6]让我停下来思考（重点是我加的）：这是一个共同的决定，我表示赞同。我为它的成功投入最多，也付出了最多的努力——但我不再认为这是我能做出最重要工作的地方。Deno 有一些好的想法，工程设计也很出色——但它最终并没有解决大问题。它被卷入了 Node 兼容性的引力井中，这迫使它的行为必须与 Node 完全一致。为什么要重新实现 Node？它已经能用了。边际性能、用户体验或安全性的提升是不够的。……我们将在一年的时间里每月发布版本，Deno 将保持 MIT 许可。如果有人想继续推进它，我乐见其成。

My brother in Christ. YOU reimplemented Node and now you’re bored? I get it was done for adoption purposes but like, that’s a solvable problem? Whatever, this ain’t my first rodeo[7]. There’s bound to be other forks but this one’s mine; I’m calling it, Ende (“end” in German). “Ende” is an anagram of “Deno” which is an anagram of “Node” and it’ll do things differently: — no more Node compatibility — no more distractions, period; that means Deploy, KV, Jupyter, &c are also getting the boot

老兄，是你自己重新实现了 Node，现在你觉得无聊了？我明白这是为了推广，但那是个可以解决的问题，不是吗？算了，这也不是我第一次经历这种事[7]。肯定会有其他分支，但这个是我的；我把它命名为 Ende（德语中的“结束”）。“Ende”是“Deno”的变位词，而“Deno”又是“Node”的变位词，它将会有所不同：不再有 Node 兼容性，不再有任何干扰；这意味着 Deploy、KV、Jupyter 等也将被踢出局。

The roadmap? Per-module permissions, sandboxes for untrusted code, post-quantum crypto in Web Crypto, better binary output, &c. I depend on Deno for all of my APIs and personal projects, and now am building a serious business on it; EOL[8]. I’m aiming for a soft launch in December so I can work out production kinks before a proper one. It’s gonna be quite the flex when Ende development is happening on EOL.

路线图是什么？基于模块的权限、不可信代码的沙箱、Web Crypto 中的后量子加密、更好的二进制输出等。我所有的 API 和个人项目都依赖 Deno，现在我正基于它建立一项严肃的业务；EOL[8]。我计划在 12 月进行软发布，以便在正式发布前解决生产环境中的问题。当 Ende 的开发在 EOL 上进行时，那将会非常酷。

Anyhoo, placeholder site for Ende[9] is up, subscribe to the mailing list if you want to be notified when it’s “official” (proper marketing and documentation websites). EOL also has a mailing list[8] if you want to know when the beta opens. I am very busy but excited. I wanted to build the Neue Internet[10] after all, looks like I’m getting my chance. 🕸️ EDIT: I’m also replacing SemVer with ChronVer[11].

总之，Ende[9] 的占位网站已经上线，如果你想在它“正式”发布（拥有完善的营销和文档网站）时收到通知，请订阅邮件列表。如果你想知道测试版何时开放，EOL 也有一个邮件列表[8]。我很忙，但很兴奋。毕竟我一直想构建 Neue Internet[10]，看来我的机会来了。🕸️ 编辑：我还要用 ChronVer[11] 取代 SemVer。