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.
Today we’re announcing that the entire Deno team is joining Cloudflare to take that work further.
Our ambition has always extended beyond the runtime [..]
Here’s what this means concretely:
- 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.
- Deno Deploy will continue operating for six months before shutting down. We will provide migration support for paying customers moving to Cloudflare Workers.
- JSR will continue operating, with its infrastructure moving to Cloudflare.
- We will continue supporting
rusty_v8and work toward integrating it intoworkerd.
pull down to refresh
related posts
If not slop, how are these both true.
By "taking that work further" they seem to only mean supporting JSR (their npm alternative) and
rusty_v8. Sounds like it's pretty strictly an acquihire and Deno is dead. I'd be surprised if JSR andrusty_v8last much longer than a year too.It's a bit sloppy, but you gotta say something when you're acquired by literally the thing you sought to make an alternative for... i.e. I think they're talking more about
celldthan about Deno:blue line is Cloudflare, green line is them
I bottom line see this as Cloudflare acquiring the competition (like FB buying Whatsapp, Nvidia buying Groq, etcetera, except this was a FOSS team)
I see. I'm way out of the loop on all this serverless stuff. Beyond the basic concepts, it always seems so platform specific and not-portable that I get spooked, ie basic computer resources are turned into a proprietary API.
So how I understand what they tried to do: offer a FOSS self-hosted runtime that is 100% compatible w/ CF (the green line is based on the amount of Digital Ocean 8GB boxes you need) so that you won't get disrupted by CF outages. Getting acquired by the thing you liberated... is a great way to cash out and give your users the finger.
Whomever ends up maintaining Deno (if anyone that isn't just a meat slave to a Claude overlord would even wanna do that) then they're likely to see hard times getting funded outside of our scene.
Oh! So it solved the problem I have with serverless stuff only to be bought out and turned back into part of the problem. It sucks because I liked many of Deno's founding ideas. I should try to find some data on founders that regret acquisitions so I can fantasize about making it well known and discouraging founders from getting acquired.
Great idea. We'll use it against you when you sell to Reddit. 😂
The request handling logic doesn’t really change between serverless implementations. In fact it doesn’t even change between non-serverless and serverless.
Proof: you can take WordPress (of all things), wrap some lines of PHP around it and have it running as an AWS lambda function.
In the end it is just a deployment strategy and you can even self host a serverless target.
this is only the first step before he comes back with Nedo, a new JavaScript runtime in Zig that fixes everything, which will try to do whatever for some years until he ragequits
10 years later he will make his final JavaScript runtime, this time using a new programming language that isn't year released. it will be called done