Node got so good I'm crawling back from Deno
Friendship ended with Deno, now Node is my best friend

After years of using Deno, a developer returns to Node for a SvelteKit client project and discovers a dramatically improved runtime: native ECMAScript support, no more require(), and a surprisingly smooth migration. Converting a static site generator from Deno to Node v26.10.0 required only swapping file system APIs and an HTTP adapter, yet delivered 15% faster builds. The post also details package management choices like PNPM and FNM, TypeScript limitations, and the reasons Deno fell out of favor.
Ultimately, Deno failed when they allowed the Silicon Valley Circus to define 'success'.
- isyouaint
I helped Deno bring the Standard Library to v1 [as a contractor] and have always loved the team and philosophy. But these days I’m saddened by what seems to be their slow decline into obscurity. After the layoffs, there seems to be no roadmap, no comms, etc. I’m just so curious as to where they’re heading and still hope the best for it. I’ve always liked Deno more than Node and Bun.
- jesse_dot_id
Node has felt fine to me for quite awhile. There was a brief time where it felt a little slow comparatively but it's been mostly ironed out. They tend to address their problems decently fast.
The Internet loves to adopt a new shiny thing, try to convince everybody else it's the right decision because it's the decision they made, and then get quiet about it. (i.e. they went back.)
- tuveson
> This restriction is philosophical rather than technical. I get it though. TypeScript is a Microsoft product. Opening that floodgate would pollute the entire ecosystem.
Bad news (well not news, this happened a while ago): https://www.cnbc.com/amp/2020/03/16/microsoft-github-agrees-...
- AgentME
Deno is still an easy pick for me because of its built-in test-runner (deno test), linter (deno lint), and type checker (deno check). I've used many different npm packages for these things in previous projects and I have no idea what the new hotness and proper configuration is for all of these things in a new node project, so I really value the simplicity of Deno for it all. Also JSR and Deno for publishing Typescript libraries is still so much easier than setting up a Typescript node project and configuring it to publish compiled code, and it gets you documentation pages generated from your tsdoc comments too, which I never knew how to do outside of JSR.
- huhtenberg
OP, if you are here, here's how the website looks in an older Firefox: https://i.imgur.com/hYh7Gat.png
- theturtletalks
With LLMs becoming prevalent, it seems people are “quitting” their projects more quickly. Not necessarily a bad thing, but just shows that the opportunity cost is too high right now if you’re building the wrong thing. Deno isn’t the wrong thing, but LLMs don’t reach for it and that’s a huge blow right now.
- tiborsaas
I'm building on Deno for the past 2 years and I have no regrets. It still delivers me why I picked it over node. Less config, less packages to install, good DX.
- raspace
Turns out the 'boring enterprise runtime' spent its time actually shipping stability while everyone else was chasing the next shiny runtime hype cycle.