logoalt Hacker News

Cloudflare acquires Deno

838 points • by ilreb • today at 1:03 PM • 463 comments • view on HN

Comments

rfgplk • today at 2:52 PM

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.

➕ show 1 reply
pmkelly4444 • today at 7:14 PM

[flagged]

patcon • today at 6:24 PM

[dead]

massimodeluisa • today at 3:18 PM

[flagged]

spprashant • today at 5:58 PM

[dead]

sick_of_slop • today at 6:35 PM

[dead]

grougnax • today at 2:21 PM

[dead]

oh_ok_lol • today at 1:20 PM

And all the VCs funding both companies celebrated the circular economy!

➕ show 2 replies
4729738210 • today at 2:12 PM

I will be avoiding Deno.

AtNightWeCode • today at 5:03 PM

It was pretty naive to stand in front of that NodeJS train.

culi • today at 3:17 PM

Welp. All tech eventually gets bought out by military contractors or grows big enough to become one.

hoppp • today at 3:17 PM

So Cloudflare killed Deno

Its no longer gonna be supported after 1 year

In 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.

➕ show 1 reply
rattray • today at 1:20 PM

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...

bilalq • today at 4:25 PM

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.