Hacker News Reader

Comment by Promarged | Hacker News Reader

I know it's javascriptjanuary.com but having this:

> node -e require('https').get('https://gist.githubusercontent.com/PurpleBooth/109311bb0361f..., b => b.on('data', c => process.stdout.write(c+'')))" > README.md

instead of plain curl seems weird to me.

View on HN

Especially as he mentioned the Unix Philosophy:

> [...], try to remember the Unix Philosphy [sic] and break it down into tiny parts that go well together, this way it's going to be way easier to initially release it and maintain it in the future.

The unix philosophy != command line tools usually preinstalled on your system.

Honestly, as an engineer that enjoys using JS and often writes cute little scripts using Node.js I fully agree that curl seems like a much better fit here.

Well, as you say, it IS javascriptjanuary.com, but I was more put off by the fact it seems it'd be nicer as this:

  node -e "require('https').get(url, b => b.pipe(process.stdout)))" > README.md

rather than this:

  node -e require('https').get(url, b => b.on('data', c => process.stdout.write(c+'')))" > README.md

(and also that there's a typo with the quoting at the beginning).

Can you 'npm i -g curljs' yet?

Reply on news.ycombinator.com