[HN Gopher] Deno's Decline
___________________________________________________________________
Deno's Decline
Author : enz
Score : 27 points
Date : 2025-05-01 22:08 UTC (52 minutes ago)
(HTM) web link (dbushell.com)
(TXT) w3m dump (dbushell.com)
| HideousKojima wrote:
| Someone in a thread here a few months back described webdevs and
| their constant obsession with changing tooling, frameworks, etc.
| as "mayflies debating politics" or something to that effect and
| it has stuck with me since. Do all these new frameworks really
| have some sort of inherent flaws that require rebuilding
| everything from the ground up every 5 years or less? Or is it
| just something inherent in the language/web (and/or the sorts of
| people who become webdevs) that causes this phenomenon?
|
| Or when JS devs suddenly discover concepts like "serverside
| rendering" and reinvent PHP and ASP.NET.
| andrewmcwatters wrote:
| I said it back when Deno was released, and I'll say it again: I'm
| not doing another JavaScript rugpull. Node.js is here to stay,
| it's mature, and if you want performance, leave it behind for Go.
|
| It was telling when you saw that basically all of Deno's
| interfaces were inspired by Go.
|
| I'm so glad that as an industry we're saying "No," to all of
| these JavaScript authors who try to yank entire ecosystems along
| with them as they go try and monetize their spin-offs.
|
| I'm too busy shipping to care.
| RainyDayTmrw wrote:
| I dunno. How much do you value isomorphism and code sharing?
| RainyDayTmrw wrote:
| This is sad news. I always found NodeJS' APIs to be a bit
| deficient, and liked Deno's better - with the caveat that they
| openly admit to copying designs from Go[1], so it's not
| necessarily original.
|
| [1]: https://deno.land/std@0.164.0
| MortyWaves wrote:
| I'm not convinced. The author has had a pretty negative view of
| Deno, JSR, etc since the beginning.
___________________________________________________________________
(page generated 2025-05-01 23:01 UTC)