News for hackers. Stuff that matters.
Re:Vercel should fork and maintain Deno by gherkinnn on Saturday November 14, 2026 @11:58AM (#50498548)
I used it for a while, it was a sane TypeScript. Most pieces came out of the box. Deno had its own formatter, test runner, standard library, server, could run TS without a transpilation step, KV DB, and god knows what else.

Switching between Deno and standard Node/TS had me thinking why can't all of Node be this nice. Over time Node adopted some of these ideas.

Deno also made some interesting choices around dependency management, its first iteration being literal links in the import statement. This bit and subsequent npm compatibility is guaranteed flamewar material.

Re:Vercel should fork and maintain Deno by DimmieMan on Sunday November 15, 2026 @07:45PM (#50512635)
Deno is boring was my biggest takeaway. Felt so nice to not have to do the version pinning ritual every few weeks because one of the half dozen dev interconnected dev components updated. Very sensible and complete environment.

They were great at standards too; if it wasn't in the Deno namespace it was standardised. Import maps and Temporal early were cool and i Learned a lot reading release blogbosts that linked to tc39 proposals.

It had some achilles heels with vite & meta frameworks and the linter wasn't great (there was a draft PR to use oxlint which would fix that) but I'm sad to see it die over the last year, the writing was well and truly on the wall before officially closing.