Deno 2.9

Deno 2.9 arrived promising a very juicy fantasy for developers: turn ordinary web code into a real desktop app, skip some of the usual setup mess, and ship it all as one file. It also teased an easier escape route from Node’s world by reading lockfiles from npm, pnpm, Yarn, and Bun directly, plus faster startup and broader compatibility. In plain English: Deno is pitching itself as the simpler, cleaner way to build apps without hauling around a giant toolbox.

But the real fireworks were in the comments, where the launch instantly became a referendum on whether anyone actually trusts Deno anymore. One camp was impressed by the ambition and saw the desktop move as bold, even overdue. Another camp basically replied, “Cute announcement, but does it break?” The harshest critics accused the project of shaky reliability, messy compatibility with older Node projects, and leadership problems, with one commenter going full reality-show confessional and blaming venture capital money for sending the project off the rails.

Then came the plot twist: one frustrated user had to post an edit of shame, admitting their angry complaint was actually caused by their own machine update going wrong. That confession gave the thread a splash of accidental comedy and a rare redemption arc. Meanwhile, the AI drama simmered too, with some readers groaning that Deno now uses Claude heavily, while defenders argued AI may be the only reason the huge compatibility cleanup is even possible. Add in the inevitable “Bun is winning” drive-by, and suddenly this release thread felt less like product news and more like a reunion episode where everyone brings receipts.