4 ms·
That phrase is heavily dangerous. > For the rest of us who are actually trying to grow businesses rather than set up IRC servers, there's HipChat and Slack. F
by Uberphallus 12y ago
That phrase is heavily dangerous.
> For the rest of us who are actually trying to grow businesses rather than set up IRC servers, there's HipChat and Slack.
For the rest of us who are actually trying to grow businesses rather than set up <insert company IT infrastructure> there's this <insert proprietary platform>.
I've heard that before from people who don't blink to have their own Gitlab/Bugzilla/Jenkins/Whatever. It's overly short sighted to dedicate resources for development support IT infrastructure, but consider resources for development communication a waste of time.
- detaro 12y agoI agree on the dangers, but I don't think they are easily comparable. GitLab/Jenkins/... are a match for the hosted alternatives, whereas I couldn't name a system that matches Hipchat or Slack without spending a lot more time on setup and customization.
- Uberphallus 12y agoAt least you can deploy a HipChat server in your own boxes, Slack is a no-go for many environments, yet still used because of a good client interface combined with a cult-like following. I've found Openfire + Spark IM to be a reasonable alternative sitting between the customizable and the convenient, and it's open source.
- s73v3r 12y agoThey're not considering resources for communication a waste of time. They just feel there's a better use for them, considering there is Slack and HipChat which do everything they want and are very simple to set up.
- kedean 12y agoThis is also a different case than jenkins/gitlab/etc, because communication of this sort doesn't need to be permanent. Unless some dev wants to use a different client, there's not really any limitations from using a proprietary platform. It's not like a few years down the road you'll want the 2014 chat logs, and even so it's not like IRC would give that to you.