3 ms·

This reminds me of the bad old days of Rails, when every man and his dog had some random hacky and myopic solution to keep Rails and Mongrel running. Just say n

This reminds me of the bad old days of Rails, when every man and his dog had some random hacky and myopic solution to keep Rails and Mongrel running. Just say no to Node/Rails/whatever specific-stuff, kids--use system level tools for running processes. Edit: removed references to "proprietary", as indexzero is correct about meaning of that.

indexzero 16y ago
That's a strange usage for "proprietary" since it's all free and open source (MIT). Either way, the nodejs child_process module is really just a light weight wrapper to execvp(): http://linux.die.net/man/3/execvp http://linux.die.net/man/3/execvp I haven't dug through the source for tools like monit, daemontools, but I'm sure near the metal they're using POSIX or similar system APIs. EDIT: There's really no reason Forever has to be node specific, I actually say that in the article: "Honestly, it's a one line fix here (https://github.com/indexzero/forever/blob/master/lib/forever.js#L356 https://github.com/indexzero/forever/blob/master/lib/forever...), but I'm not sure if users want to put 'node' in-front of every command." I'll file your comment as a +1 for that feature ;)