Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- Node has a bright future. See e.g. Platformatic's "Watt" server^1 for an example of pushing it forward.
1. https://platformatic.dev/ and https://github.com/platformatic#-watt--the-nodejs-applicatio...
by chrisweekly - I guess between the original Node and the many alternatives that aren't Node (that I, a former PHP guy using Go for side projects, wish would gain more traction) there isn't enough of a niche for a "mostly like Node, but with fewer warts" project?by rob74
- I can just echo that thank you!
Even as a big Deno "hater" due to their anti-package manager stance on the basis of URLs that leads to a sleuth of dependency attacks, I must say that Deno and the people behind it have undoubtedly pushed the space forward on many aspects!
by hobofan - > Bun joined Anthropic ten months ago. The tempting conclusion is that the alternative-runtime experiment is over & Node has won by default.
Well, Bun is surprisingly better and convenient than before
by yayugu - And thank you for the coolest, funniest, smartest product announcement vid ever made: https://www.youtube.com/watch?v=swXWUfufu2w
- Thank you deno!
You are added to the list of projects I thought would really become essential to my work but slowly faded away. Another one, for example is rethinkdb.
At least Deno actually caused some movement in the node world, just like io.js.
by egeozcan - I'm really sad about the announcement and that the Deno runtime as it was is going away. I'll definitely be following and likely using an active fork if it presents one.
I've been using Deno a lot for straight shell scripting. Being able to link directly to dependencies and run without a separate install step or node_modules directory is huge. The fact that it's a single binary download and can self update is so nice too.
I'm not sure if these features are similar for Bun or not. I'm just sad about the whole thing.
by tracker1 - > Deno 1.0 shipped in 2020 on the original terms, & then spent the next four years walking them back one piece at a time. First the deps.ts convention, one file that re-exported every URL: a manifest in all but name. Then lock.json, an integrity hash per URL: a lockfile. Then import maps, so you could write bare specifiers again.
I object to two of these categorisations.
deps.ts was a convention, not a built-in runtime feature. If you want to follow the convention, that's fine. It's just a regular old typescript file!
Import maps were not Deno walking back, but implementing a web platform feature. Parity with browser JS was a standout feature of Deno from the beginning. This was walking forwards if anything.
However, broadly, the story is indeed one of Deno moving away from its opinionated roots towards pragmatism (drop-in replacement for Node).
by crabmusket