Hacker News Reader

Comment by javajosh | Hacker News Reader

Speaking of which, is anyone using deno (https://deno.land/) for anything real yet?

Nothing real, but I am watching closely. I write everything in TypeScript anyway and it is annoying figuring out what adapters to use to get testing libraries working and VSCode debugging, and debugging tests, etc.

If they implement Go-style concurrency that would kick this project up to the next level.

> If they implement Go-style concurrency that would kick this project up to the next level.

I don't think that would work given the fact that it still runs V8's event loop.

Node has to be painful enough for people to make the switch. I don't think we've hit that point yet.

I can't think of any node.js painpoints. Can you list some examples? I've been coding in it at a high level for the past 5 years.

Same! What pain points?

I got downvoted to hell and back for saying node.js is easier to develop in/be efficient in/be productive in than Haskell. Can you believe that?

When I think secure I think

  import { serve } from "https://deno.land/std@v0.19.0/http/server.ts";

It would be better to integrate something into Node.js instead of inflating a new economy balloon!

What do you think is happening when you `npm install` or `yarn add` a package?

`npm`/`yarn` have hash checks when using the lockfile (side note: you should be using `npm ci` in your deployments so it doesn't install newer versions). Maybe there could be a lockfile system for webpack that would verify a file like the one they suggest doesn't change between installs and systems.

Doesnt deno also have a lockfile?

That's why I don't want to use it personally, it's all in the imports. Making things a pita when you want to just upgrade something.

Yeah, we need a new JS ecosystem, let's rebuild all our stuff using deno instead node, because it was a quiet year and we have all recovered from the JS fatigue.

Reply on news.ycombinator.com