News for hackers. Stuff that matters.

A comment on Node.js 13.0. Parent comment

Re:Node.js 13.0 by snek on Tuesday October 22, 2019 @05:28PM (#21328663)
You should not parse the stdout produced from console functions. It is for producing human-readable information. If you want machine-consumable data, you should use something like benchmark.js.
[ Parent | on HN ]
Re:Node.js 13.0 by BillinghamJ on Thursday October 24, 2019 @03:30AM (#21342463)
That's true of stderr output. You should be able to parse stdout though - otherwise how are you meant to use piping etc
[ Parent | on HN ]
Re:Node.js 13.0 by nothrabannosir on Tuesday October 22, 2019 @07:15PM (#21329431)
How far we have strayed from the days where Unix tools were meant to be used as a stdlib, called through stdin and out. It makes me a little sad.

Classic HN comment on this topic: https://news.ycombinator.com/item?id=6530180

[ Parent | on HN ]
Re:Node.js 13.0 by snek on Tuesday October 22, 2019 @11:44PM (#21330860)
Not that far. Node has process.stdout/process.stdin/process.stderr. It's just that the console API is for debugging.
[ Parent | on HN ]