Hacker News Reader

The "Don't talk about deno" release. Quite an interesting feature list. I'm really interested if wasi + a permission prescription + package authorization might allow us sharable cli tools like git hooks and filters that we can trust.

View on HN

Why are you referring to it as that?

because one of deno's key selling points is restrictions on permissions, on what can a running script do to its environment.

deno's built-in test runner is also a big selling point for me, and Node.js 20 is declaring theirs (node:test) to be stable.

The big new feature is a sandboxing with explicit CLI flag opt in to permissions, exactly like deno pioneered. Except there's zero mention of deno as a clear inspiration of the feature.

Kind of reminds me of deno's support for package.json after realizing they needed the features.

Not needed at all. In fact, I've never used and will never use a package.json in any of my Deno projects.

They added the feature to "enabl[e] developers to transition from existing Node projects with ease."

https://deno.com/blog/v1.31#packagejson-support

I don't understand that description, but I'll take your word for it.

Yeah, not sure why a release note would mention a competitor?

Isn't Deno a dinosaur? I thought it's ancient!

Reply on news.ycombinator.com