Cloudflare acquires Deno
For years, we’ve been working to make building server software simpler. We questioned how modules could be distributed, what security guarantees a JavaScript runtime could provide, what belonged in a complete toolchain, and how easily an application could be distributed as a standalone executable. Compatibility with Node.js became an important part of that work too: our users wanted the Deno improvements while continuing to plug into the existing JS ecosystem. The team and community built a runtime that brought these capabilities together and challenged assumptions about what JS development could look like.
多年来，我们一直致力于简化服务器软件的构建过程。我们探讨了模块应如何分发、JavaScript 运行时能提供哪些安全保障、完整的工具链应包含什么，以及应用程序如何能轻松地作为独立可执行文件进行分发。与 Node.js 的兼容性也成为了这项工作的重要组成部分：我们的用户既希望获得 Deno 带来的改进，又希望继续接入现有的 JS 生态系统。团队和社区共同构建了一个运行时，将这些功能整合在一起，并挑战了人们对 JS 开发模式的固有认知。
Today we’re announcing that the entire Deno team is joining Cloudflare to take that work further.
今天，我们宣布整个 Deno 团队将加入 Cloudflare，以进一步推进这项工作。
Our ambition has always extended beyond the runtime. I wrote about this in my JavaScript Containers blog post: compute, storage, and communication working together, without every application assembling its own infrastructure.
我们的抱负始终超越了运行时本身。我在关于 JavaScript 容器的博客文章中写道：计算、存储和通信应协同工作，而无需每个应用程序都自行组装基础设施。
With Deno Deploy, we took another step towards that goal. We wanted to make running applications as straightforward as possible. But building and operating Deploy also showed us how much complexity remained underneath that developer experience. I wanted to simplify that layer, too.
通过 Deno Deploy，我们向这一目标又迈进了一步。我们希望让运行应用程序变得尽可能简单。但构建和运营 Deploy 的过程也让我们看到，在开发者体验之下仍隐藏着巨大的复杂性。我也希望简化这一层。
This led to celld. Building on the Cloudflare Workers programming model, celld lets developers build distributed applications from the start while making the system simple to operate. What excites me greatly is that the scaling is built into the programming model, rather than infrastructure each app has to assemble itself.
这促成了 celld 的诞生。基于 Cloudflare Workers 编程模型，celld 让开发者从一开始就能构建分布式应用程序，同时使系统易于操作。让我感到非常兴奋的是，扩展性被内置到了编程模型中，而不是每个应用程序都需要自行组装的基础设施。
The progression from Deno to Deno Deploy to celld explains why this move makes sense to us. At Cloudflare we’ll combine our work with that of the Workers and Durable Objects teams. We want to make this programming model the default way to build servers, whether you run on Cloudflare’s network or your own infrastructure.
从 Deno 到 Deno Deploy 再到 celld 的演进，解释了为什么这一举措对我们来说意义重大。在 Cloudflare，我们将把我们的工作与 Workers 和 Durable Objects 团队的工作相结合。我们希望使这种编程模型成为构建服务器的默认方式，无论您是在 Cloudflare 的网络上运行，还是在自己的基础设施上运行。
Joining also means choosing where to focus our effort. We’ve decided to put our future development work into this shared platform rather than continuing to develop a separate runtime and hosting service. We know this is a consequential change for people who have built on Deno.
加入也意味着要选择我们努力的方向。我们决定将未来的开发工作投入到这个共享平台中，而不是继续开发独立的运行时和托管服务。我们知道，对于那些基于 Deno 构建应用的人来说，这是一个重大的改变。
To everyone who contributed code, built businesses on Deno, reported problems, and trusted our direction: thank you. Here’s what this means concretely:
对于每一位贡献代码、在 Deno 上建立业务、报告问题并信任我们方向的人：谢谢你们。以下是这一决定的具体含义：
The need for better abstractions is especially acute with AI. Durable Objects bring together capabilities that are particularly useful for agent harnesses: inexpensive, serverless execution, persistent state, WebSockets, and a high-level JavaScript interface. This is what I’m most excited to explore and why celld focuses on Durable Objects.
在人工智能领域，对更好抽象的需求尤为迫切。Durable Objects 汇集了对智能体（agent）开发特别有用的功能：低成本、无服务器执行、持久化状态、WebSockets 以及高级 JavaScript 接口。这是我最期待探索的方向，也是 celld 专注于 Durable Objects 的原因。
Kenton Varda and I explain more in our joint post on the Cloudflare blog. If you’re building agents at scale and want to run them on your own infrastructure, please reach me now at ry@cloudflare.com.
Kenton Varda 和我将在 Cloudflare 博客的联合文章中做进一步解释。如果您正在大规模构建智能体并希望在自己的基础设施上运行它们，请立即通过 ry@cloudflare.com 与我联系。