Deno

“the security benefits Deno has over Node are still the number one reason, we're picking Deno over Node at work”

“And now if you heard it, Deno is dead. 1 more year of support and they all got hired to work at cloudflare instead”

“Some of the early decisions, like their initial refusal to fully support package.json and the npm eco-system, made me unsure of their suitability as the basis for a business.”

“This is disappointing, and really makes me question what is the point if even open source is now this easily enshittified”

“I feel it leaves a bitter flavor how Ryan Dahl pushed so hard for Deno and Deno Deploy for years, just to let them die”

“I use Deno daily and while it's true that it's in this weird position where it's not sexy like bun or enterprise-y like node, it has a great developer experience.”

“to take advantage of its permissions system, and instructed it to use Deno instead of Python or bash commands. It's worked pretty well.”

“it's Go-like `std` library, so that building basic apps didn't result in a spaghetti web of dependencies”

“Feels like I should have either gotten perfectly matching versions, or error messages (with commands) to update node.”

“While we have a lot of test coverage and we use tests directly from Node.js codebase, we just don't catch everything.”

“Deno has very complicated import resolution, so building my own import resolver to be compatible with it is a bit of a pain.”

“they've gone in the route of just taking Node native libraries and what not just because they gave up on working out the compatibility”

“There is already a strong, safe runtime that's not vibe coded, called Deno, that more people need to check out.”

“they tried to ditch npm and found this limited their adoption so significantly that they had to patch it back in”

“Node compatibility getting better with every release makes the transition a lot easier for existing projects.”

“deno is like node without all the shitty parts. It's just so simple and productive and has so much good stuff built in.”

“well deno has 'allow-read' 'allow-write' kind of permission, so if something tries to read from my ~/.ssh or other important folder, it can just block it”

“is performant and has dramatically improved node compatibility while exposing a proper permission broker api”

“it uses Deno as the runtime to constrain network, filesystem, environment, and other types of access at runtime”

“The Deno sandbox is the answer here — network access is restricted to an allowlist, and the execution environment has scoped permissions.”

“I can reference any repository modules directly, use a shebang in the top of the script with self/executable, and no install step.”

“If you use deno as your default runtime, it's almost Go-like in its simplicity when you don't need much.”

“Deno with URL imports mean you can have a single-file script with external dependencies and it just works.”

“Coming out swinging with 2.0 and then decreasing regions and rewriting the product that makes you money soon after was certainly a choice.”

“Deno asking you to throw out package.json on day one was basically asking you to rewrite your entire build config”

“Url-based imports are a bad idea as soon as you go beyond writing your entire program in a single source file”

“All the breaks from the first system in the name of “we’re doing it right this time” probably killed the momentum.”

“work on the experimental-strip-types option in Node was inspired/energized by a desire to try to catch up with the DX improvements found in Deno”

“being able to put your whole "project" in a single file that grabs dependencies from URLs reduces friction a surprising amount”

“it's great that you can reference your dependency modules directly as well as not needing a separate install step like node”

“with a .ts file with Deno you can pull in a complex dependency with one line and write logic more succinctly”

“Deno is also either: 1. Pivoting to Cloud (for AI Agents to use Deno) 2. Looking for an exit to an AI lab or infrastructure partner.”

“It's a single portable, self-upgradeable executable and your shell scripts can directly reference the repositories/http(s) modules/versions it needs to run”

“I've come to use Deno typescripts for anything more complex than what can be easily done in bash or powershell.”

“The best option I've found for this use case (ad-hoc scripting with third party dependencies) is Deno.”

“Things like Deno, Bun, even Go and Python make writing quick, small, modern server sides so much quicker, easier and safer.”

“Today there seems to be a lot of parity, and I think things like JSR and strong importmaps support start to weigh in Deno's favor.”

“I tried several times to port Node projects to Deno. Each time compatibility had "improved" but I still didn't have a working build after a few days of effort.”

“Deno itself is a JS runtime that often runs, at my behest, code that I did not myself write and haven't vetted.”

“Deno also allows the bundle to be optionally compiled into a native executable that can run without having to install Deno separately.”