alt Hacker NewsThis is a wild detail to just bury at the bottom. So many companies went all-in on Deno in recent years. Some even did major migrations off Node.js. Sucks for them I guess, but that's always the risk in chasing the shiny new thing over sticking to the old and dependable.
Replies
Exactly why any company that cares about long term maintenance should stick with Node.js except in cases that justify alternative runtime.
I wouldn't be surprised if Bun is abandoned at some point as well.
(Which is why I am happy to see new runtimes but never care enough to seriously use or adopt them.)
How will this affect those of us relying on those projects? It's not just those companies but also the customers of those companies.
I guess "joining" was the key word here. But I'm not particularly surprised now that I see it meant acquihire.
Anybody who has been bitten by the many issue with Yarn over the years can tell you, just stick with stock tools and deal with it.
At least open source gives them an opportunity for the community to find a way to support it going forward. But I suppose that's just table stakes these days.
I wonder how much they have financially contributed to Deno.
Asking as a non-JS person - what's the cost and effort to switch?
It's why I usually look more closely at the comments here than at the story for stories like this.
I was really surprised that cloudflare was acquiring deno to be honest, I have written about this here before, Deno was always sort of dead to me due to how little they cared for compat of all kinds (nodejs, CJS, backwards). It was refreshing to see bun care a lot about it (well, now its on a different path in other ways).
Then I read that paragraph, and it made more sense that they're acquihiring + killing.
Radical idea here, but maybe those many companies could _fund_ the development of key components of their infrastructure.
>So many companies went all-in on Deno in recent years.
Companies went all-in in a barely established niche player with 1/100 the traction, instead of sticking with Node, and even better an LTS Node, and are now surprised?
Do they also do their front-end in Dart?
Honestly migrating back is trivial now. It just isn't that big of a pain.
> So many companies went all-in on Deno in recent years.
They should hire a few devs to develop it then.
Seems like an extremely risky thing to do. Luckily they can keep maintaining it and improving it if their business is truly dependent on it.
You can migrate off deno in a single day. It's not a big deal.