jlouis8

I simple have to ask this question (full disclaimer: longtime functional nerd with specialty in Erlang):

On a scale from totally fine to batshit crazy, where do you place Erlang/OTP? Where do you place Node.js on the same scale? And why?

(this in the vain hope I can get Bryan on one of his famous rants :)

Thank you for your answer. It is peculiar, because I normally tout Erlang debuggability as one of its strengths. It essentially has the like of DTrace built in (and DTrace support in the C parts to boot nowadays). You can query the live system while it is running in production by connecting to it. It isn't the most intuitive platform however, and sadly many of the good old tried and true UNIX-book tricks doesn't work, since the environment is so different.

As for clients, the major one I've seen is that many of them forgets to set TCP_NODELAY, which shows itself as a nice little latency hiccup in tcpdump :)

Nice you solved the problem by ripping it out and replacing it with something you know. If there is any rule to go by it would be "pick the system on which you are familiar with its peculiarities, be it Illumos, FreeBSD, Linux, ..."