Slacks growing usefulness is predicated on the fact that people build bots for it.
It's not that IRC can be as good as slack -- IRC is NOT the same kind of thing as slack, they are different. IRC is a protocol, slack is not, slack is a product. My point is that the right product needs to be build AROUND IRC to make it viable/interesting.
From the previous comment, it seems like the features people are loving slack for are:
- Well designed interface
- File sharing
- Inviting/sharing channels with people
- Functionality provided by bots
Is that incorrect? I'm sure that list is incomplete, is there anything very significant I left off?
Please reply to posts directly for the sake of keeping the thread tidy. If you don't see a reply link for a post, click the timestamp (e.g. "17 minutes ago") to go to the permalink view for a given comment, where a reply box will be available.
That's a neat trick, and not one that I knew about. I would also like to know why the reply button doesn't appear at times -- I presumed some kind of rate-limiting.
To you and the others curious about why the reply button doesn't show up, there is a buffer period after a reply appears before you can reply to it, to mitigate flame wars and such. It's usually a few minutes.
If you mean the fact that you can circumvent this, then I'm not sure. It's possibly intentionally left in so that more experienced users have a way around that limitation.
- offline mode integrated
- search
- usable mobile clients
- inline images
- notification control
- usable interface for private and group chats
- access control and authentication integrated
Anything can be built but irc has huge fragmentation of clients, so dev focus is thinly spread, developers have not apparently been interested in changing the ux for decades, and most of the (small number, despite what this article says) users like it how it is.
Slacks growing usefulness is predicated on the fact that people build bots for it.
It's not that IRC can be as good as slack -- IRC is NOT the same kind of thing as slack, they are different. IRC is a protocol, slack is not, slack is a product. My point is that the right product needs to be build AROUND IRC to make it viable/interesting.
From the previous comment, it seems like the features people are loving slack for are:
- Well designed interface
- File sharing
- Inviting/sharing channels with people
- Functionality provided by bots
Is that incorrect? I'm sure that list is incomplete, is there anything very significant I left off?