Yeah I don't understand why "name your (short callback) functions" gets repeated as a truism so much. Do people have stacktraces that are missing line numbers?
Re:Debugging Node.js in Production
by alessioalex on Friday December 04, 2015 @04:17PM
(#10679199)
Line numbers don't help you with memory leaks, seeing the name of your function there does.
This. They don't show up in heap dumps and sometimes CPU profiles.
How do you easily glance at a stack trace and know if it is your own code or a 3rd party library's code? Named functions definitely help a lot.
Re:Debugging Node.js in Production
by Killswitch on Friday December 04, 2015 @04:16PM
(#10679191)
Because at a glance, it's easier to see the path of the file as an identifier than the name of the function. Function names are not unique throughout the codebase and dependencies. Lots of dependencies have the same named functions.
And every difficult to debug bug hasn't been related to knowing which functions are in the stack, but are instead related to figuring out why frameworks do something or race conditions and so on.
I just find it surprising that people are having problems with anonymous functions in stack traces, when I've never seen that.