404 Deno CEO not found

Posted by WhyNotHugo 10 hours ago

246 points | 174 commentspage 5

andrewstuart 6 hours ago|

The problem Deno faces is that nodejs is “good enough”.

Pray you never have a “good enough” competitor.

I felt it should have aimed to be a 100% drop in replacement for nodejs then innovated on top of that.

nulltrace 1 hour ago|

Tried moving a monorepo off Node once. The runtime swap was the easy part. What killed us was the 50-odd package.json files with node-specific stuff baked in. Conditional exports, postinstall scripts, engine constraints, pnpm overrides. Bun got this right by just eating all of that as-is. Deno asking you to throw out package.json on day one was basically asking you to rewrite your entire build config before you even got to try it.

IshKebab 8 hours ago||

I really hope this is premature because Deno is easily the best thing to happen to the JS/TS ecosystem in years.

I agree with all the comments saying this is unnecessarily critical. We're getting an amazing tool totally for free. Quit complaining.

I would not be surprised if they get bought by one of the big AI players anyway, given the weird purchases of Bun and Astral.

mrcwinn 8 hours ago||

What nonsense. Does it count as a “clapback” when the CEO responds sensibly and takes responsibility? This is just pointless snark.

barrrrald 5 hours ago||

Who hurt you?

fnord77 8 hours ago||

> The harsh truth is that Deno’s offerings have failed to capture developers’ attention. I can’t pretend to know why — I was a fanboy myself — but far too few devs care about Deno.

I never heard of Deno until today. So perhaps this was a marketing failure.

qcautomation 6 hours ago||

[dead]

robutsume 9 hours ago||

[dead]

themarogee 9 hours ago||

[dead]

themarogee 9 hours ago||

[dead]

MuffinFlavored 9 hours ago|

> What’s next for Deno?

Who cares? Why does the world need so many fringe tools/runtimes? So much fragmentation. Why does every project have to be a long-term success? Put some stuff out if its misery. Don't waste the time of the already few open-source contributors who pour hours into something for no good reason.

steve_adams_86 8 hours ago||

Deno is much more than a fringe tool. It's a genuine improvement in many ways.

MuffinFlavored 7 hours ago||

The world doesn't need a dozen JS runtimes.

The world doesn't need a dozen JS engines.

The world doesn't need many dozens of Linux distros.

The world doesn't need a handful of BSD distros.

The world doesn't need many dozens of package managers.

The world doesn't need hundreds of JS frameworks.

The world doesn't need dozens of programming languages or chat protocols or CI/CD systems.

The world doesn't need dozens of init systems, service managers, display servers, audio stacks, universal app formats, build tools/bundlers.

Deno may have dragged the JS runtime space forward, fully agree. Maybe it served its purpose and it is time to say goodbye.

steve_adams_86 6 hours ago|||

If Deno moved things forward, doesn't that suggest that we do need efforts like this to support ongoing progress? There doesn't seem to be strong evidence to the contrary in the JS ecosystem.

balamatom 5 hours ago|||

The world doesn't need so many people or anything they have to offer it.

balamatom 5 hours ago||

I'd argue that the mainstream, lowest-common-denominator tools are the ones which waste people's time. (Especially when they're backed by an incumbent. Deno, on the other hand, clicked immediately.)

More comments...