Deno v1.27 - Hackdot

Re:Deno v1.27 by triyambakam on Thursday October 27, 2022 @03:01PM (#33362377)

I'm an eager and early adopter of Deno. I however look forward to ecosystem improvements, and the interop with npm is helpful. I was working on a side project recently that was a simple CRUD app and I just ended up going with Express on Node after fighting with Oak on Deno for a few days. It was still in the way enough to slow down the rapid fire development process that happens when you're still figuring out an idea.

[ Parent | on HN ]

Re:Deno v1.27 by shafyy on Thursday October 27, 2022 @03:25PM (#33362723)

I'm also dipping my toes in Deno (with Fresh) for a side project. Just curious, what were the blockers you came across with Oak?

[ Parent | on HN ]

Re:Deno v1.27 by kitsonk on Thursday October 27, 2022 @04:46PM (#33363800)

Yeah, I would be interested to understand what challenges you had with oak too.

[ Parent | on HN ]

Re:Deno v1.27 by JoyrexJ9 on Thursday October 27, 2022 @04:43PM (#33363764)

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

[ Parent | on HN ]

Re:Deno v1.27 by encryptluks2 on Thursday October 27, 2022 @06:17PM (#33364775)

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

[ Parent | on HN ]

Re:Deno v1.27 by schemescape on Thursday October 27, 2022 @08:27PM (#33365946)

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.

[ Parent | on HN ]

Re:Deno v1.27 by jstummbillig on Friday October 28, 2022 @02:45AM (#33368387)

> 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.

[ Parent | on HN ]

Re:Deno v1.27 by jcuenod on Thursday October 27, 2022 @11:15PM (#33367223)

I'm using deno (with oak) for a side project and it's great. I experimented with bun as well, but came back to deno because I got frustrated with bun's segfaulting (this was pretty early after their announcement).

[ Parent | on HN ]