[JoyrexJ9]

Yeah NH gives a warped lens on how ready these runtimes & frameworks are for real work. Threads about Deno and Bun pop up almost weekly, yet in my experience they remain a long, LONG way from the stable (and admittedly stale) experience we have with Node and NPM

[jstummbillig]

> Yeah NH gives a warped lens on how ready these runtimes & frameworks are for real work

I think it's more that HN is warping reality on how ready they are for real work. We are shaping what is going to happen next in tech, and how quickly, by being eager and ready to give things a try and, in a mix of above average skill and curiosity, being able to make it work at a fairly sophisticated level, despite its current shortcomings.

[encryptluks2]

I don't know that they are made to.

Npm packages already do too much, with package.json being used to run scripts that have permission to do nefarious tasks to relying on C libraries.

If I were to use Deno it would be with the understanding that I'd need to find dependencies that are generic and standard... Not expect everything from npm to work by default.

If I used either I'd specifically look for dependencies that are standard enough to not matter or

[schemescape]

Hopefully it has changed, but when I was using Deno, there wasn’t a standard for TypeScript libraries that worked in both environments (due to Deno requiring file extensions on imports and tsc requiring no file extension on imports). There was a workaround using import maps, but it’s not tenable for large libraries.