Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sometimes it's ok to think "this project isn't for me" and just leave it be. The cynical-security-concern act is boring.


Contrary to the impression I seem to have given you, I'm actually super excited about Deno and am planning to write my next MVP app in it.

That means that I am actually a lot more vested into it, and if I want to put it in production, then I have to be concerned about things like this.

When somebody says they think X is broken, and they present a solution Y which they say is better, I am definitely entitled to ask why they think Y is better when I can't see the difference.


But you don't seem to be genuinely seeking answers, at least not in this thread. Does seem you're already convinced of the projects faults.

You're entitled to your opinion, of course. I had to read through the docs to understand their module system and intent. And I find it very exciting.


Security is literally the main selling point of this thing. Otherwise just use node.


It’s one of the selling points. One of the main points I took away was

” We feel that the landscape of JavaScript and the surrounding software infrastructure has changed enough that it was worthwhile to simplify. We seek a fun and productive scripting environment that can be used for a wide range of tasks.”

Sounds intriguing to me. As a fan of starting projects of as simply as possible, I will certainly be tinkering with Deno.


There are a lot selling points. To me, the main one is typescript with no build.


  yarn global add ts-node prettier
  echo 'alias deno="ts-node"' >> ~/.zshrc
  echo 'alias deno-fmt="prettier --write"' >> ~/.zshrc
Deno provides a standard library, good defaults, top-level async-await, doesn't break browser compatibility, better API to integrate with runtime.

Internals are nicer but that's with anything without ugly legacy.

They are working to get node_modules work in deno so I am kind of worried that it will be nodev2 all over.


Clearly they have never dealt with JavaScript build tools and npm. A complete nightmare.


Who hasn't? Isn't this precisely one of the pros of Deno?


Yes. That's why I said that.


Promise-based APIs sold me.


Strawman security questions without an understanding of the tool are not very useful.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: