Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • I feel it leaves a bitter flavor how Ryan Dahl pushed so hard for Deno and Deno Deploy for years, just to let them die within 1 year and 6 months respectively. Thankfully I don't have any codebases that heavily use Deno features, otherwise this would be a steep curve now.
    by bennett_dev
  • A lot of the comments are on sunsetting Deno, but the more interesting part is merging the celld model into workerd.

    I've been following celld since it was announced. Bootstrapping both durability and coordination off object storage simplifies so many things for self-hosting. (Yes, ironic that self-hosting has a cloud dependency, but in this case I think justified because S3 has become a widely supported protocol that you can run yourself too).

    Will be curious to see the details on exactly how that model makes it into workerd.

    by ryanrasti
  • So the developer tooling consolidation/acquisitions continue... hmm!

    - Cursor -> SpaceX

    - Astral/uv -> OpenAI

    - Stainless -> Anthropic

    - Bun -> Anthropic

    - Astro.js -> Cloudflare

    - Deno -> Cloudflare

    - VoidZero (Vite, etc.) -> Cloudflare

    - NuxtLabs -> Vercel

    - Hugging Face -> NVIDIA

    - ... what else?

    by sixdimensional
  • RIP, my favorite JavaScript runtime, and thank you. You were too secure for this world.

    What kind of business move is this for Cloudflare? celld is a more complete Cloudflare-at-home runtime than current workerd. What does Cloudflare stand to gain from commodizing Workers?

    I'll say that although I'm not really a Cloudflare Workers user, I've been eyeing workerd and celld with interest. The idea of a complete backend in a box appeals to me (see also: PocketBase, Algernon). At the same time, the acquisition means that another company won't acquire Deno for celld.

    by networked
  • "Deno development effectively shut down via a Cloudflare acquihire" would be a better headline.
    by coldtea
  • I'm so bummed about this. Deno is by far my favourite JS runtime. I could sense this coming for a while now, but I was hopeful and just waiting to see what happened. Here we are. I'm glad I don't need to get off the runtime immediately. Sad we won't see any innovation like we did in the last 8 years or so.

    I hope workerd at least adopts Deno's security mechanisms so it functions as a better sandbox.

    One of my favourite projects of 2026 was a configurable LLM harness built around using deno as the runtime. The idea is that the configuration builds a state machine-driven program which is bundled into a binary that can only provide access to the I/O your code explicitly needs. I used it primarily to build interactive programs for colleagues which allow some LLM magic to occur without needing to worry about what they would do with Claude Desktop handling the same data or accessing the same machines and so on. It also allowed for testing local LLMs in deterministic patterns. How do they reason about what to do next when they can evaluate the possible states they can enter, based on the current context? It was really fun. Now I don't really know how I'd rebuild it, knowing I wouldn't use Deno. Maybe that's worth learning anyway.

    by steve_adams_86
  • I loved early Deno and am sad to see it die. I invested heavily in the Deno ecosystem because of Ry’s initial vision for it.

    But I stopped because I saw this coming the moment they changed course and started putting npm compatibility as a priority. Deno’s surface area went from beautifully simple to very bloated. I think they felt the pressure of VC funding and just gave up on rebuilding Node from first principles.

    The silver lining is that early Deno was so good that Node copied some of its features. So at least we have a better Node now.

    by sholladay
  • > We will support the Deno runtime for another year with monthly releases containing bug fixes and security updates. After that year we will end our development of the Deno runtime. Deno will remain open source, and we welcome others who want to continue its development.

    So unless someone else picks up development, Deno will no longer be supported.

    by theodorejb

Explore Birbla archives