Reports of Deno's Demise Have Been Greatly Exaggerated
1–10 of 210 posts
Re: Reports of Deno's Demise Have Been Greatly Exaggerated
#2This is likely in response to https://news.ycombinator.com/item?id=43863937
Re: Reports of Deno's Demise Have Been Greatly Exaggerated
#3Whenever I read a blog post assuring me that something is not how it looks, it turns out to be exactly how it looks at the end.
BTW, I don't use deno and haven't been following any news whatsoever so this is simply a shitty statement from an outsider. It is interesting that I tested deno a couple of times but kept using node until bun came around and I basically switched to bun. I can't say why exactly.
Re: Reports of Deno's Demise Have Been Greatly Exaggerated
#4Post is by the CEO and doesn't really address the criticisms around Deno, just seems to justify their own internal decisions (or his?). Seems like Deno products work really well for Deno though!
Re: Reports of Deno's Demise Have Been Greatly Exaggerated
#5Most developers weren’t deploying simple stateless functions. They were building full-stack apps: apps that talk to a database, that almost always is located in a single region.
I wonder if this is true in general for most people on serverless these days. If so, whether this is what the original intention of this movement and whether these people just don't want to deal with docker/k8s.
Re: Reports of Deno's Demise Have Been Greatly Exaggerated
#6I was super-excited about Deno right up until they threw away their earlier commitments and added backwards compatibility for node and all the shite that comes with it.
The whole selling point for me was that deno was node without the bullshit and baggage, but they dropped that and basically just turned it into node with built in typescript support and a few other minor things like the permissions.
Similar story with bun.sh - node backwards compatibility (although not using V8).
Does anyone know of a server-side typescript scripting engine that is not trying to be backwards compatible with node?
Re: Reports of Deno's Demise Have Been Greatly Exaggerated
#7I’m sure a bunch of the criticism of Deno is exaggerated. But there’s something fundamental holding me back from investing my time in Deno, or Bun for that matter: they’re both VC funded.
The post is a good illustration of why that matters. Very little of it is about Deno itself, instead it’s mostly about the paid-for services Deno Inc offers. They have to prioritise and chase that because their investors want to see financial growth.
It’s the same reason they abandoned the idea of Deno being a fresh start in the JS ecosystem (an idea I loved) and instead started patching in Node compatibility layers. They had to reduce friction, not add to it. But for me that compromised the reason for using it in the first place.
Node has many flaws. And it’s boring. But its existence doesn’t depend upon the whims of random investors who might decide to pull the plug at any moment. So I’m just going to stick with it.
Re: Reports of Deno's Demise Have Been Greatly Exaggerated
#8Post is by the CEO and doesn't really address the criticisms around Deno, just seems to justify their own internal decisions (or his?). Seems like Deno products work really well for Deno though!
What criticisms of deno do you think went unaddressed?
Re: Reports of Deno's Demise Have Been Greatly Exaggerated
#9Whenever I read a blog post assuring me that something is not how it looks, it turns out to be exactly how it looks at the end. BTW, I don't use deno and haven't been following any news whatsoever so this is simply a shitty statement from an outsider. It is interesting that I tested deno a couple of times but kept using node until bun came around and I basically switched to bun. I can't say why exactly.
I agree also as an outsider. These sorts of "meta" discussions always smell of spin aimed at investors and usually are not good news for customers. Customers generally care about things like product and long term reliability and stability. These meta things always have the tone of Monty Python's "Bring out your dead!" segment.
Re: Reports of Deno's Demise Have Been Greatly Exaggerated
#10Doesn't inspire confidence.
I guess we’ll see soon enough what Deploy will become since that's "imminent".
KV is dead if they've no desire to develop it out of beta and are working on something new. No reason to ever use it for a new project now.
Fresh is being refactored with an alpha in "late Q3 2025 (likely September)". It was a fairly basic framework to being with. The no compilation/build step was the only interesting idea and that's going away.
The runtime is actively developed but I find this statement amusing:
> We’re not chasing feature parity with other runtimes.
The release notes on Node/NPM compatibility would suggest otherwise.