I used this at work today. Someone had asked what our webapp's sysreqs were. I said that network connection was very unlikely to be a problem, but it really struggled when set to GPRS. Now, I think it's unlikely that anybody would be using it on that, but it's still good to know that it's an issue.
Team communication: Teams need to interact in a variety of different ways: public groups/private groups, fixed groups/ad-hoc groups, groups/1-2-1. HipChat supports a variety of different ways of interacting, and does so in a way that's easy to use.
People nowadays use a variety of different devices (and classes of device). HipChat has a range of native clients, plus a web based one, and so can be used on most of the devices that people want to use it on.
(We use Slack, but I've tried and liked HipChat too)
I've never really got my head round RFCs, but 4180 is only informational, not a standard. I have used exactly your argument before though, and will again. Have also been on the other side and needed to convert horribly inconsistent data to fit it.
I know you're just being glib, but here are some answers:
* build doesn't mean compile
* you can compile your build process and then use that to actually run your build
* the benefits of typed languages go beyond catching errors at compile time