3 ms·
The sense I get is that he's trying to differentiate Slack from the general category of enterprise chat and want to communicate it's more than that. I do know s
by 8ytecoder 7y ago
The sense I get is that he's trying to differentiate Slack from the general category of enterprise chat and want to communicate it's more than that. I do know small teams that use Slack to automate their business process workflow that require some manual steps. There's a valid argument that it's yet to realize its full potential in that regard.
However, I agree with the general sentiment that Slack must be profitable by now and if their messaging isn't reaching the target audience it's their fault and their fault only. Not to mention the ridiculously high valuation.
- ethbro 7y agoWhy anyone would willingly plug an opaque, overly complicated, poorly optimized, externally controlled failure point into their tech stack is beyond me.
- journalctl 7y agoWhen I go to work every day, I don’t want to have to worry about whether or not our chat server is up. My job isn’t to manage chat servers, it’s to manage all the servers we actually need to get our shit done. I don’t want to get paged at 2 AM because some XMPP server is down, which will, the next morning, prevent everyone from communicating. Sure, Slack goes down too, but I can make some coffee and let an entire team of dedicated people fix it; it’s their emergency, not mine. Only host things if you really need to, and only if you have the resources to support them. Unless you want to add “manage chat servers” to your list of core competencies, just buy something and move on. Our business isn’t managing chat servers. All we need is an IM service so we can communicate and get our stuff done. Slack, for all its faults, works for us, and frees up our time to focus on the problems we actually want to solve.