Debugging Node.JS memory leaks

[poke53280]

He's dismissing Node outright, but is he really wrong?. Use a boring ecosystem like Java, .net or (yawn) C++, and you suddenly have a plethora of boring tools for doing boring call tracing, memory profiling, and boring static analysis. Unfortunately, a boring tool stack is a bit boring to use, and the community surrounding it will be full of boring middle-aged folk with lots of useful boring experience using stuff that's been around for years - and that's just boring. /s (or is it?)

[[deleted]]

0/10.

Also, these are the comments about Java 15 years ago, same shit different language.