Top
Best
New

Posted by ilreb 10 hours ago

Cloudflare acquires Deno(deno.com)
985 points | 512 commentspage 3
greeniskool 4 hours ago|
I wonder how this will affect Bunny's competitor to Cloudflare Workers, Edge Scripting [1] -- which runs on Deno.

[1] https://bunny.net/docs/scripting/

stillpointlab 6 hours ago||
I'm very sad Deno is going away, even though I've never used it nor did I plan to use it.

It is a bit hypocritical in a sense. Similar to how I was sad that a local restaurant recently closed down. In the past two years I went there maybe three times total. But I just liked having it there as an option.

Deno had a ton of good ideas but I just never felt confident that it would have the lasting power. Some of the early decisions, like their initial refusal to fully support package.json and the npm eco-system, made me unsure of their suitability as the basis for a business.

But I always wanted them to succeed. In the same way I always wanted Heroku to succeed even though I never used their service.

More options are better. But I guess "use it or lose it" applies. Did I dodge a bullet or contribute to the downfall?

multisport 10 hours ago||
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.
DannyBee 8 hours ago|
It's almost certainly not worth it. Having less software that you can keep more reliable is almost always worth it over having more software just because it's 10% faster or whatever. This isn't always true but it's mostly true.
255kb 3 hours ago||
It seems VC money is not really compatible with open source
mahboi 3 hours ago|
Maybe they all learned their lesson from Docker giving away the entire product for free
chrysoprace 3 hours ago||
It's very sad. I was excited about Deno from day one, and I wanted to see it succeed.

Deno's ability to run TypeScript files - stripping types - was arguably implemented in Node because of Deno. The consolidated tooling approach was a good attempt at solving tooling fragmentation that Node suffers from.

I think for Deno to succeed, it would've had to have been under a non-profit and maybe that can still happen.

herrherrmann 3 hours ago|
It would certainly be nice if someone continued the work. But I wouldn’t hold my breath for it. Seems like an unthankful job (although I’m sure many projects using Demo now would be happy if it’s still supported, at least).
huqedato 9 hours ago||
RIP Deno. Goes into the bin, after Bun.
po1nt 9 hours ago||
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.
adamddev1 9 hours ago|
What did you transition to?
schnebbau 8 hours ago||
AI.
rootnod3 7 hours ago||
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.

mysterydip 4 hours ago||
I just learned of Deno yesterday when setting up some software for the first time. I wonder how many applications depend on it behind the scenes?
JaceComix 9 hours ago|
Node always felt so annoying to deal with. I was really excited when Bun and Deno were coming up. Pour one out.
More comments...