Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Deno 2.9

deno.com

Post reply on HN
Print view View original

31–40 of 63 posts

Re: Deno 2.9

#31

Post by jdxcode »

pixel_popping wrote: post #15
bartlomieju wrote: post #10

Earlier quoted context omitted.

Gee, sorry to hear that. It's Bartek from the Deno team here. This is really a whack-a-mole. We currently present the latest stable Node.js version (26.3.0) so the error is not correct - I bet it's probing for something stupid like no of arguments a certain function supports. Is your project open source so I can take a look myself?

You can have AI do way more automated testing in a loop, let cheap models run 24/7 so all edge cases can be found over time by pulling random repos, you must make sure the agent is entirely autonomous, ask another agent to make a list (also in a loop so it keeps appending to it) and another agent that try to fulfill "run it with Deno".

I think node already does this (sans AI), idk where the code lives but deno could probably just use the same list of repos

Re: Deno 2.9

#32

Post by nwhit »

catapart wrote: post #26
bartlomieju wrote: post #10

Earlier quoted context omitted.

Gee, sorry to hear that. It's Bartek from the Deno team here. This is really a whack-a-mole. We currently present the latest stable Node.js version (26.3.0) so the error is not correct - I bet it's probing for something stupid like no of arguments a certain function supports. Is your project open source so I can take a look myself?

unfortunately, while the project is in the public domain, it's pre-alpha so I haven't made the repo public yet. but the project is structured the same as another public domain project I've built, and I just checked to make sure it has the same issue. I've gone ahead and made that project public so you can give it a try[0]. but, just to be clear, I don't think the message is wrong? The Node version on this machine is…

What node version do you have installed? I cannot reproduce the issue on that repo, I've tried with node versions all the way back to node 12.

Re: Deno 2.9

#33

Post by Recursing »

Tiberium wrote: post #9
Recursing wrote: post #8

Earlier quoted context omitted.

node randomly broke production for us last week https://github.com/nodejs/node/issues/63989 not sure it can be considered "stable and won't break things like this between minor releases"

Welp, guess the only option is to stay on some single version then and hope it doesn't get critical security issues...

That node release was to fix security issues...

Re: Deno 2.9

#34

Post by pier25 »

MoonWalk wrote: post #5
Tiberium wrote: post #2

To be honest, Deno was cool in the past (I even somewhat promoted it on HN in some comments), but nowadays I'm disappointed in their lackluster approach to stability and testing (specifically in Node compat). I recently hit multiple Node compatibility regressions in Deno that were hard to debug, and it doesn't help that they use Claude for everything now, from actual fixes to writing blog posts (even this one). For e…

Well if Node compatibility is your big deal then yeah, why not just use it? I started a new project on Deno to avoid the NPM mess. Node compatibility was a distraction for the product. I'm tired of everything depending on Node. Assuming that everybody uses it is lazy.

> Node compatibility was a distraction for the product

I've gone back and forth on this point over the years.

Yeah, Node compat has probably affected the rest of the product. I imagine at some point they (or their investors) freaked out because adoption wasn't happening. And the reality is it really doesn't matter if your product is better when nobody is using it.

In retrospect I think it would have been a better decision to target Node compat from the start like Bun did. An impossible option at the time given Deno started trying to make something different from Node.

Or maybe the problem was simply they couldn't afford low adoption after having investors on board.

Re: Deno 2.9

#35

Post by catapart »

nwhit wrote: post #32
catapart wrote: post #26

Earlier quoted context omitted.

unfortunately, while the project is in the public domain, it's pre-alpha so I haven't made the repo public yet. but the project is structured the same as another public domain project I've built, and I just checked to make sure it has the same issue. I've gone ahead and made that project public so you can give it a try[0]. but, just to be clear, I don't think the message is wrong? The Node version on this machine is…

What node version do you have installed? I cannot reproduce the issue on that repo, I've tried with node versions all the way back to node 12.

here's a dump of the console:

```

catapart@snake:~/Development/magnitce-code-example$ deno install

Warning The following packages are deprecated:

┖─ npm:boolean@3.2.0 (Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.)

catapart@snake:~/Development/magnitce-code-example$ deno task dev

Task dev vite

You are using Node.js 20.11.1. Vite requires Node.js version 20.19+ or 22.12+. Please upgrade your Node.js version. error: Uncaught (in promise) SyntaxError: The requested module 'node:util' does not provide an export named 'parseEnv' at file:///home/catapart/Development/magnitce-code-example/node_modules/.deno/vite@8.1.0/node_modules/vite/dist/node/chunks/node.js:11:46

    at async CAC. (file:///home/catapart/Development/magnitce-code-example/node_modules/.deno/vite@8.1.0/node_modules/vite/dist/node/cli.js:706:27)
```

also: I'm using Linux Mint, if it matters.

Re: Deno 2.9

#36

Post by phaser »

I am the freaky outlier that's actually excited about this.

My city builder game, Microlandia[1], runs on Deno. The game's graphics and UI is a Three.js/React app, but the guts of the game are in a "sidecar" process that is a `deno compile` typescript executable.

On Mac, there's a Tauri shell that runs both client and server, and for Linux and Windows we use Electron, (Tauri proved to be quite problematic except when in macOS)

Why on earth did I choose this cursed stack instead of a "proper" game engine? Well,

Turns out developing the simulation in typescript with a performant sqlite driver hot reloads very fast and with a light code editor and my browser open on a second window I see the stuff updating live as I make it.

Deno has a good VSCode extension with test helpers and a fast language server. WebGPU is good enough for me to write any cool shader I can think of and I don't miss any capability of a game engine.

More importantly, not using Unity/Unreal brought back to me the joy of game development that I had lost due to and horrendous UI-driven workflow that takes me back to Macromedia Flash (yes, I am that old). Oh, and the licensing.

And I know I could switch to Bun with small changes in code but Deno has never got in my way. Maybe it's because I avoid using libraries at all costs (and don't need much).

Also, Typescript/React is such an amazing language for building a complex tycoon/simulation type of game that deals with a lot of data and displays it. Anyone who's worked on Unity knows it's the dark ages for UI over there.

I'm unsure if i'll port the game to Deno Desktop anytime soon but if I start a game again I will use this stack again, as my game engine, this time without Electron or Tauri.

1. https://microlandia.city

Re: Deno 2.9

#37

Post by WorldMaker »

catapart wrote: post #26
bartlomieju wrote: post #10

Earlier quoted context omitted.

Gee, sorry to hear that. It's Bartek from the Deno team here. This is really a whack-a-mole. We currently present the latest stable Node.js version (26.3.0) so the error is not correct - I bet it's probing for something stupid like no of arguments a certain function supports. Is your project open source so I can take a look myself?

unfortunately, while the project is in the public domain, it's pre-alpha so I haven't made the repo public yet. but the project is structured the same as another public domain project I've built, and I just checked to make sure it has the same issue. I've gone ahead and made that project public so you can give it a try[0]. but, just to be clear, I don't think the message is wrong? The Node version on this machine is…

The release notes here indicate that if a script shells out to node and you have a node installed Deno lets the installed node run instead of its own shim.

Re: Deno 2.9

#38

Post by pixel_popping »

jorvi wrote: post #30
someguyiguess wrote: post #19

Earlier quoted context omitted.

You're getting downvoted because "AI bad" but this is actually a good idea.

Because none of that requires "AI". You can use a script to clone GitHub top NPM repos (by whatever measure), and then 'simply' try to migrate them to Deno and log all the errors and warnings. Maybe you compile those errors in a neat list with an LLM, and ask it to emphasize things it considers important. But even that can be done inside the script with loglevels and maybe some regex. Parent is getting downvoted beca…

A script made by AI, digested by AI, organized by AI? Let's call it what it is.

Re: Deno 2.9

#40

Post by undefined_void »

conartist6 wrote: post #29
bartlomieju wrote: post #20

Earlier quoted context omitted.

Sure, we also managed to close ~30 outstanding issues with this rewrite and set us up to reach ~90% node:http compatibility, so overall I consider it a success.

AI lets people be reaaaaaaally "productive" when leaning into entirely the wrong work. Deno has no future if all it wants to be is a clone of node, so it just seems to me like your work is to speed the collapse

> A "node:http" regression caused by a PR fixing many of outstanding issue. Author explains and apologizes.

> "Deno has no future"

I think there may be other things bothering you? These comments aren't really productive and discourage maintainers to even continue replying.

Disclaimer: I am a maintainer.

Post reply on HN