Cloudflare acquires Deno

Holy shit, I used to work on the Workers Runtime Team and I'm surprised!

RIP

So both major (and the only meaningful) possible Node alternatives have been absorbed into proprietary monoliths in the last year. We all know how well the Joyent years went, RIP to open source innovation at this point.

can yall stop selling out to cloudflare? The continued consolidation of the internet/tech is wild.

huhyyy

is this Cloudflare signalling they're going to hard pivot to being an AI company?

</3

> Deno sells out

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

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.

What a shame. Guess me and the clankers will be maintaining a fork now

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.

uh oh

[flagged]

[dead]

[flagged]

[dead]

[dead]

[dead]

[flagged]

[flagged]

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

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

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.

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

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.