Deno joins Cloudflare and announces the end of its runtime development

Deno’s entire team is joining Cloudflare, but developers using its JavaScript and TypeScript runtime have good reason to look beyond the welcoming announcement. The move comes with a deadline for official runtime maintenance and a much shorter runway for its hosting customers.

In its October 9 announcement, Deno says it will release monthly bug fixes and security updates for another year. After that, the team will stop developing the runtime. The project will remain open source, and others are welcome to continue its development, but there is no promised replacement maintainer in the announcement.

Deno Deploy customers face a more immediate problem. The hosting service will continue operating for six months before shutting down, with migration support available to paying customers moving to Cloudflare Workers. Anyone running an application there now has a migration project to plan, regardless of how enthusiastic the companies sound about their new direction.

Ryan Dahl explains that the team will focus its future development on a shared platform with Cloudflare rather than maintaining a separate runtime and hosting service. JSR, its package registry, will continue operating with infrastructure moving to Cloudflare. Support for rusty_v8 will also continue, with plans to integrate it into Cloudflare’s workerd runtime.

Cloudflare’s announcement centers on making its Workers programming model easier to run outside its own network. Dahl and Bert Belder will lead an effort to combine code and ideas from celld, Deno’s distributed application project, with workerd. The goal is to make self-hosting Workers and Durable Objects a supported option for developers.

Durable Objects bring application execution, persistent state, and communication together. For a chat application, for example, individual objects can handle different channels and their data, helping distribute the workload. That model appeals to Dahl because developers otherwise have to assemble and coordinate more infrastructure themselves.

Cloudflare also acknowledges an existing weakness. Although workerd is open source, its Durable Objects implementation currently supports only a single instance and cannot scale across machines. Kenton Varda admits the company did not build enough surrounding services and tooling to make self-hosting practical for more users. The Deno team will help address that gap.

Making Cloudflare’s technology easier to operate independently could give developers more options. Still, that future benefit does little to erase the immediate disruption for people who chose Deno and now need to reconsider their plans.

Open source gives the runtime a chance to continue beyond its creators’ involvement. Whether a community takes on that work is another question. For existing users, the useful information here is the maintenance schedule, the hosting shutdown, and how much work moving elsewhere will require.

☕

Support independent tech journalism

NERDS.xyz is independently owned and operated. If you enjoy my coverage of Linux, AI, hardware, cybersecurity, and tech culture, consider supporting the site on Ko-fi.

Support NERDS.xyz
Written by

Brian Fagioli ✔

Technology journalist and founder of NERDS.xyz

Brian Fagioli is a technology journalist and founder of NERDS.xyz. A former BetaNews writer, he has spent over a decade covering Linux, hardware, software, cybersecurity, and AI with a no nonsense approach for real nerds.

Leave a Comment