Hacker News new | ask | show | jobs
by mcintyre1994 871 days ago
The other side of it is if you want to distribute your code not as a server. If you write a CLI in Node + TS + ... then it might be pretty fiddly for someone to clone that repo and get it running locally. You'll certainly have to document exactly what's needed.

Whereas with Deno you can compile to a single binary and let them install that if they trust you. Or they can `deno install https://raw.githubusercontent.com/.../cli.ts`, or clone the repo and just run `deno task install` or `deno task run`. For those they need to install Deno, but nothing else.
1 comments
mcpeepants 871 days ago
> then it might be pretty fiddly for someone to clone that repo and get it running locally

with node + TS, it is straightforward (and common) to generate JS output at publish time for distribution. then, using the CLI tool or whatever is only a `npm install -g <pkg>` away, no extra steps.

sure it's not a single binary, but I'd argue _most_ users of a general CLI utility don't necessarily care about this.

link