HN

Comments (320)

• Menu

  theodorejb
  > 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.
• anon
  undefined
• Menu

  sholladay
  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.
• Menu

  coldtea
  "Deno development effectively shut down via a Cloudflare acquihire" would be a better headline.
• Menu

  networked
  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.
• bilalq
  Time and again, staying on the mainstream node/npm stack continues to be the validated choice. I've seen this happen with io.js, bun, and deno. The situation has been similar for yarn/bun and most alternatives on the package manager side.Of course, that's not to say the work done on these platforms was wasted. The divide around io.js was meaningful to getting things moving faster and change the governance structure. Deno and bun both showcased things Node could be doing better and some of that was folded back in.And in spite of all those past experiences, I still find myself using pnpm over npm today. I'm sure npm will continue to evolve and eventually the critical features of pnpm will just be part of core npm. But the gap today is massive enough that pnpm over npm feels critical. The disk usage and performance wins are life-changing for daily work and CI flows.
• Menu

  bennett_dev
  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.
• Menu

  TheRoque
  Damn. Deno is a super old project, in 2018 the Nodejs creator did the talk "things I hate about NodeJS" and introduced Deno. It's 8 years ago now, and clearly even though the project was known by most Node users, it didn't gain any traction at all. I don't even remember "the bad parts" that Deno tries to solve, were they that bad at all ? Anyways Node will keep evolving and implement new features, new standards, optimization. I think it's super risky to move to an alternative. In the age of the LLMs, if you wanna get out of Node, you better translate all to native Go or Rust.
• Menu

  ryanrasti
  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.
• pmkary
  What is it with everyone buying runtimes? — P.S. Deno always felt like it is going to be abandoned, you can't build your work on this much shaky ground...
• Menu

  flohofwoe
  To summarize my feelings: Shit!Deno's ability to import directly from a package registry or even git repo in a standalone TS script without requiring a package.json or similar 'meta-data' file was actually really nice for shell scripting stuff. AFAIK node.js still can't do anything similar?
• yellow_lead
  Remember "choose boring technology"?I had to evaluate Deno vs. Bun vs. Node for a project two years ago, and chose Node. I think Deno has good ideas but often times these projects cannot reach escape velocity, especially when they're constrained by VC motives.
• Menu

  phaser
  I’m happy if this means Deno is able to get a second impulse. I use Deno daily and while it’s true that it’s in this weird position where it’s not sexy like bun or enterprise-y like node, it has a great developer experience. a no-surprises runtime that does a lot of interesting things the right way (like compile to desktop to a browser-less webgpu runtime), the vscode extension is flawless and overall the perfect balance of batteries included without bloat.of course i’m only talking about deno, the technology not deno, the cloud service.
• Menu

  duesabati
  Insane, I'm deeply saddened and embittered, I don't want to go back to NodeJS and I don't find any advantage in Bun. I guess this is my sign to just get off of JavaScript entirely.
• pimterry
  The Cloudflare side is also worth a read: https://blog.cloudflare.com/deno-joins-cloudflare/
• rootnod3
  All of this just re-informed my believe to stay with true and tested systems that have survived decades. C if I fell confident and Common Lisp otherwise. Both standardized, have been around for ages, and they don’t disappoint.I feel bad for anyone that now relies on Deno. And as good as Cloudflare might be for some things, I also feel bad for anyone relying on them.
• Menu

  tiborsaas
  Congrats on the exit :)Finally, the next step of forking Node is up for grabs:Node > Deno > Done (anyone?)
• jppope
  This is a real bummer. Work never adopted Deno but I love their model, security posture, and the standard library. I've been less interested in typescript recently, but it has turned into the default for frontend.On the plus side, cloudflare will get access to some fantastic talent, who can hopefully put their effort into building a better web.
• sheept
  I’ve been using Deno’s permission system as a sandboxed replacement for ‘python -c’ for my agents. Hopefully a better supported runtime (in any language) adds a similar permissions system in the near future.
• Menu

  multisport
  I'm very surprised they are not running with the runtime. That seemed like Deno's secret sauce? The rest of it is very aligned with Cloudflare already, deploy, kv, workers, etc seems like the lower hanging fruit.
• Menu

  AznHisoka
  I think the biggest thing Cloudflare needs to buy is some sort of Postgres-database service. They've already cornered the market for everything front-end/serverless
• wg0
  This might not be seen in much favourable light by many but IMO Cloudflare has the most elegant serveless PaaS as I have seen to date.The design and architecture is extremely minimal to the point that all of it can be explained on a single A4 page with a 14pt font including D1 + Durable objects. And I hope that it stays that way.It has all the primitives that you can wish for to build a software system on top of it be it queues, long running jobs, workflows, pipelines, email handlers, cron jobs and even built in AI models ready for you to be invoked.ATM - it is extremely cheap, reliable, simpler and more capable than anything out there. Deno itself had very little scope anyway because almost no developer tooling is sellable in this environment even more so post AI. Therefore, it is going to accelerate the Cloudflare platform to be the best in class and hopefully not complex and bloated.
• 6thbit
  Didn’t they have a flashy lawsuit to free the JavaScript trademark? What happens to that now?No indication cloudflare would pursue that yet that I see.
• Menu

  aravindputrevu
  Last year it was bun, and now it is - Deno!What's happening to JS platforms? I thought Deno has a much better approach to building a platform.
• singularity2015
  Deno did bring lot of good ideas and hope some of them will flow into Node, especially full typescript type stripping, package less imports to name a few.Also worth calling out that if you want to disrupt a major player, you need to be 10x better, not just 2x.Either way, congrats team. Hope you going on to build something great at Cloudflare.
• Menu

  bicepjai
  Genuine question. Why are companies buying our runtimes ? What is the advantage ? Maintaining open source and having more adoption in specific softwares like runtimes and programming languages helps keep software more robust and reliable right ? Am I getting something wrong.
• Menu

  po1nt
  I was rooting for Deno so much as I was fighting with node for years. Luckily I made full transition from JS last year and not comming back.
• Menu

  vmg12
  If this was done to kill celld as a runtime that would be unfortunate.edit: my reaction was too soon, it seems like they will be explicitly working on making workerd an open source self hostable runtime
• huqedato
  RIP Deno. Goes into the bin, after Bun.
• sandelz
  A bit worried what will become of https://github.com/denoland/rusty_v8 as it still is the best maintained (?) and featured binding of V8 for rust.
• afavour
  I'll sound smug saying it but this is always, always inevitable from the moment Deno took VC investment. Either it was going to be successful enough to take over everything (and it wasn't going to be) or it would end up acquired/shut down.I know Node is boring but it's not going anywhere.
• JaceComix
  Node always felt so annoying to deal with. I was really excited when Bun and Deno were coming up. Pour one out.
• ravenstine
  Man, this year has been nothing but bad news for me. This is disappointing, and really makes me question what is the point if even open source is now this easily enshittified or "killed by [insert big tech co here]." I've spent years now using Deno nearly exclusively for new projects, and saw it as the most sane JS server runtime. This also makes me hesitant to use anything with Ryan Dahl's name on it ever again.
• mattvr
  Inevitable for a project like this when you take VC money, unfortunately.
• Menu

  chaosharmonic
  Well this is fucking depressing.So what's the story with JSR sticking around then? Does it already see meaningful use among people using Workers, or do they just really want an escape hatch in case we see more long-term issues with GitHub and NPM?And does it at least mean the stdlib will see continued development?
• culi
  Can't believe they bought out Vite and now Deno. All our toolchains are getting bought out by military contractors
• csiegert
  I’m disappointed that they discontinue the Deno runtime. It really is a joy to use.I think they ran out of money and joining Cloudflare was their only remaining option.
• bluegatty
  Wow. Just about to choose Deno for something. That not only makes me rethink Deno but ... rethink a lot of things ...
• Menu

  gen2brain
  I have no idea anymore what is happening, and none of the blogposts seem to explain that either. So, if I am to start a new JS or TypeScript project or whatever, what should I choose and why? One runtime used a lot of tokens to rewrite Zig project, one was already Rust, one bought, one rewritten in Go, what is going on?
• Menu

  agp2572
  This shows that there was no money to be made in their business model and they had to sell to make up for the years or losses accumulated.
• Menu

  randall
  This is actually awesome news believe it or not. I'm excited b/c i think there's a lot of potential in the world w/ deno's team being on solid footing w/ cloudflare.I know the runtime is in trouble, but i'm not as worried tbh b/c the principles deno championed are going to keep going.
• hoppp
  So Cloudflare killed DenoIts no longer gonna be supported after 1 yearIn that case Deno is not joining cloudflare, it's got eaten.I invested a lot and use deno everywhere. Can't trust anything these days.Lets fork it into opendeno. I like to have an all-in-one swiss army knife tool.
• Menu

  dzonga
  my recent comment [0]: was deno was the only other tech player building a proper serverless platform to bring Cloudflare workers in an open source manner.will they continue that work ?[0]: https://news.ycombinator.com/item?id=49977056otherwise this is a proper acquisition. t
• crsv
  Grats on the bag.
• Throwaway123129
  Can we rename title to "Deno is winding down" ? It's not joining cloudflare. the people are
• dpc94
  Disappointing news to see it shut down, but maybe the writing was on the wall after they laid off some of their folks.I've been using deno for years and built some nontrivial services in it. When deno added support for npm packages, the early days were pretty rough. I ran into lots of issues with packages and spent a lot of time reading random github issue threads. It's been pretty smooth sailing for the last year or so though.At least I can use ai to help migrate off of deno.https://dbushell.com/2026/03/20/denos-decline-and-layoffs/
• Menu

  paaloeye
  It's only OpenAI which doesn't have an in-house modern runtime
• dgellow
  Congrats to the team! Sad to see deno go away, it’s a really great tool
• Menu

  mbStavola
  No idea why CF wouldn't just have them to continue working on Deno indefinitely...
• notnullorvoid
  > 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.Extremely disappointing...
• j45
  One step towards a $25K github replacement?
• hackersnooze1
  Gotta say the fate of Deno has been pretty disappointing I had high hopes for it
• zmj
  This is awesome. The Cloudflare platform is great; being able to run more of it locally is a definite plus.
• Menu

  HeadOfProbing
  Deno was a good idea in the Old World of software development before LLMs, and simply doesn’t make sense anymore.
• Menu

  DonHopkins
  Announcing eDon, my rewrite of Deno in Rust!Edit: Yes, but it's not named after me, which this fork fixes.It's going to be the first JavaScript runtime to natively support Super Intelligence APIs.I'm having an LLM replacing all occurrences of "ai" in every API with "si", in the hopes that OpenSI or SpaceXSI will acquihire me.
• anon
  undefined
• anon
  undefined
• anon
  undefined
• NicoJuicy
  https://blog.cloudflare.com/deno-joins-cloudflare/> The Deno team is joining Cloudflare to radically simplify self-hosting Workers and Durable Objects so developers can use the same primitives in more places.Well, that's pretty big news actually.
• gxcsoccer
  Cloudflare is playing a big game ...
• its-summertime
  Disappointing. Everything I want to express about this is impolite.I guess I can say that this means Deno won't ever have a much needed Python 3 moment.
• Menu

  asar
  really wondering what role celld played in the negotiations
• asgr
  </3
• Menu

  h1fra
  Congrats. But also terrible news for the ecosystem; this project was a bit doomed from the start, and they acknowledge it multiple times (implicitly), but nice to have competition, I guess.Ultimately I only trust Node.js to succeed. Bun being too deep into "shipping anything that increases usage".
• Menu

  Jgrubb
  Honestly, this motion right here is the death of open source - the rug pull. I no longer can trust any open source project won't get bought up and sunsetted. I'm glad open tofu and valkey and Linux exist to serve as a counter example but this makes me sad.
• Menu

  kentonv
  Please be sure to read the post on Cloudflare's blog, it's not just fluff:https://blog.cloudflare.com/deno-joins-cloudflare/TL;DR: Ryan and co. will be merging celld with workerd to create one first-class open source self-hostable runtime for Workers and Durable Objects. In the post I explain in the post why, contrary to what you might think, this is good business for Cloudflare and we're very excited about it.
• classified
  R.I.P.
• evbogue
  Congrats Ry
• jpmonette
  huhyyy
• victorbjorklund
  RIP
• ramesh31
  So both major (and the only meaningful) possible Node alternatives have been absorbed into proprietary monoliths in the last year. We all know how well the Joyent years went, RIP to open source innovation at this point.
• sharktheone
  sorry, but who even is still working on Deno? All my friends who used to work on Deno got fired
• Menu

  cyanydeez
  is this Cloudflare signalling they're going to hard pivot to being an AI company?
• nullstyle
  What a shame. Guess me and the clankers will be maintaining a fork now
• Menu

  wosined
  > Deno sells out
• Menu

  rvz
  > 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 Deno is going to be unsupported and will no longer be maintained and will be discontinued.It looks like "written in Rust" is not enough for a selling point and lost out to the fierce competition against Bun.
• rfgplk
  Sorry, but even factoring in that this acquisition carries over the existing customer base and goodwill, this is still **** (censored because I aim to stay polite). Deno is factually speaking a one to two week project at this point (proven by the numerous JS runtimes already on the market). I genuinely do not see how this makes any sense whatsoever. If Cloudflare was seeking to hire the team behind Deno they could have done it at a fraction of the price paid. This, naturally, assumes they did pay anything and I can't be bothered to look up the exact $$$ amounts.
• massimodeluisa
  [flagged]
• anon
  undefined
• grougnax
  [dead]
• anon
  undefined
• Menu

  oh_ok_lol
  [flagged]
• 4729738210
  I will be avoiding Deno.
• culi
  Welp. All tech eventually gets bought out by military contractors or grows big enough to become one.
• rattray
  As a bystander, I'm excited by this. I don't know what it'll be, but I have a sense some interesting, powerful, and secure new ways of shipping code could come from this marriage...