So unless someone else picks up development, Deno will no longer be supported.
From what is likely going to happen is that Deno will be donated to the Linux Foundation to avoid this.
edit: my reaction was too soon, it seems like they will be explicitly working on making workerd an open source self hostable runtime
They would rather have Deno pursue an acquisition instead of shutting down and losing their investment.
The only questionable detail about this announcement is it was for an undisclosed amount. Make of that what you will.
[0] https://www.sec.gov/Archives/edgar/data/1477333/000119312519...
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.
My point is, even if Bun stayed on Zig, Deno still struggled to compete regardless of the language used.
Though nodejs was even then quite solid in it's position, so maybe it would not have made a difference.
Finally, the next step of forking Node is up for grabs:
Node > Deno > Done (anyone?)
Extremely disappointing...
CF has its own quirky serverless technology and has no interest in funding any competition, even/especially in such sad shape as Deno is
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.
Most of us are here because we’re curious what it means for Deno specifically and FOSS TypeScript runtimes in general, since Bun was also acquired.
But I do have a strangely high trust in the individuals involved (you, Ryan, Sunil, others), even though I am a bit perplexed by CloudFlare's incentives or economics
Which is to say: I am choosing to be optimistic :)
Caveat, am commenting before reading, mind you -- just my general reaction to mergers in a world that never cleaves :)
EDIT: though this has also probably deflated a lot of the good-faith conversations I was having with gov-adjacent Europeans about celld being a boon for the moment of heightened European sovereignty, where EU data residency isn't necessarily considered enough distance anymore.
Ultimately I only trust Node.js to succeed. Bun being too deep into "shipping anything that increases usage".
For my projects, I am used to maintaining package manager configuration, bundlers, linters etc.
So I never had much interest in looking into benefits of Deno or bun.
Then I read that paragraph, and it made more sense that they're acquihiring + killing.
phaser•45m ago
of course i’m only talking about deno, the technology not deno, the cloud service.
weli•41m ago
phaser•9m ago
pimterry•39m ago
Bad news, sorry, the article says:
> 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.
Sounds like Celld will live on within workerd, Deno is over.
mzajc•39m ago
From TFA: 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.