News for hackers. Stuff that matters.

A comment on Ditching Go for Node.js. Parent comment

Re:Ditching Go for Node.js by MuffinFlavored on Thursday November 23, 2017 @02:49PM (#15767412)
> Tooling is a lot better in go ecosystem for understanding CPU and memory consumption, so if/when you run into into issues with Node you're going to be in a world of pain (this is basically a large portion of my job in a large node.js code base in the $day_job).

Is there no movement to change that? What about `node --inspect`?

[ Parent | on HN ]
Re:Ditching Go for Node.js by iends on Thursday November 23, 2017 @03:52PM (#15767722)
node —-inspect is a great debugger but last I looked the tooling around memory wasn’t very good. As far as I know, the best practice is to use Ben Nooordius’ heapdump tool (which is super flakey between bugs and Linux oom killer) or lldb with a node plugin. Joynet has/had some cool stuff for illuminos based OSes and IBM seems to be working on some tooling but it’s not there yet.
[ Parent | on HN ]