7 engineers on Hacker News describe using Deno first-hand: 2 endorse it, 3 regret it, 0 are mixed.
“Being able to link directly to dependencies and run without a separate install step or node_modules directory is huge.”
endorse · personal · tracker1 · 2026-10-16 · source ↗ · wrong label?“Deno felt to me like they were building a parallel ecosystem that I don't have a ton of conviction in”
regret · personal · kabirgoel · 2025-12-02 · source ↗ · wrong label?“We migrated all of our RPA scripts to Deno and then this popped up and killed our hopes and dreams.”
regret · production · sebmellen · 2025-01-29 · source ↗ · wrong label?“the differences are really trivial.”
endorse · personal · gorbypark · 2023-11-30 · source ↗ · wrong label?“I've tried to get Deno to work before in production, but it had so many compatibility issues last I tried it would take weeks or months to refactor things”
regret · production · mpoteat · 2020-12-10 · source ↗ · wrong label?“Not in production, but for my hobby programming, Deno 2 is not a big change from Deno 1.”
neutral · personal · skybrian · 2024-11-10 · source ↗ · wrong label?“I chose to rewrite in Deno rather than sticking with traveling ruby.”
neutral · production · ccouzens · 2022-12-25 · source ↗ · wrong label?