27

Deno team is joining Cloudflare and will soon stop working on the Deno runtime and Deno Deploy

top 10 comments
sorted by: hot top new old
[-] dragnucs@lemmy.ml 3 points 1 day ago

I did in a different thread than this acquisition is less bad if it had been acquired by Microsoft and maybe deno is still better than Node. This announcement makes it clear that what we want from Deno is going to fade away and the situation is much worse fhan6what I had hoped for.

[-] bigmclargehuge@lemmy.zip 10 points 2 days ago

Damn. Seems like the kiss of death. I really liked Deno. I wonder what Cloudflare is trying to gain by ending it.

[-] sanitation@lemmy.today 1 points 1 day ago

was only a matter of time with those vc companies

[-] SsxChaos@lemmy.ml 3 points 1 day ago

I was so hyped for deno3 to be released, now instead of that I got bombarded with these news, I just got used to it. Now after a couple years of avoiding bunjs I guess I'll have to switch after all.

[-] mindbleach@sh.itjust.works 3 points 1 day ago
[-] victorz@lemmy.world 3 points 2 days ago

Wow, first bun went full AI (i.e. I won't use it), and now this. I guess I'll just start node or spidermonkey when I want to use a JS REPL. Shame about not being able to use TypeScript anymore though.

[-] arty@feddit.org 4 points 1 day ago

With Node you can use TS now

[-] spartanatreyu@programming.dev 1 points 1 day ago

Yeah, but node has no standard library which deno had, and no security model which deno also had. (technically node has a "security model" in name only since it's broken by design)

[-] arty@feddit.org 2 points 20 hours ago

This didn’t seem to be a problem for Victor though, did it?

[-] victorz@lemmy.world 1 points 1 day ago

Ooh, shiny! ✨

this post was submitted on 10 Oct 2026
27 points (100.0% liked)

JavaScript

2830 readers
4 users here now

founded 3 years ago
MODERATORS