He gives a nice reasoning in the last paragraph:
Slack is a walled garden. Their proprietary API is defined by them and only implemented by them. They can and will shut off parts you depend on (like the IRC+XMPP gateways that were just shut down).
Is this really true though? Doesn't Mattermost have a slack-ish-compatible interface?
This is the exact reason why I don't like Slack - It takes up WAY too much screen estate. At least with IRC I can format it in a way that I prefer, AND be able to use the rest of my screen for other tasks.
Slack has its merits, but plain IRC also works fine.
The same people that prefer slack because they never really tried IRC, might say they prefer slack because it allows them to write BOTs.
BOTs in irc is easy, there are 3 kind of bots:
- bots that interact: User types something in a channel or via private message. The bot will receive that message and the user that typed it. then it will parse the message and take an action. Examples of interaction messages:
-- msg to bot: google this: "time now ?" (then the bot connects to google and makes a query and replies to this message): UTC 10h20 -- msg to bot: reboot
- bots that say stuff: You are on a chatroom and then all of a sudden a bot joins and says something ie. "Your new website has been updated". OR, "Someone made a pullrequest on github, please somebody go there and accept it"
- a mix of those 2: the bot will say stuff and also accept/interact commands
IRC is really simple. The bot simply reads text and takes action. Or, just take action and talk on the channel. Its completely diffrent from slack bots because it is simpler it will not need the programmer to set up a WEB SERVER in order to receive messages from slack. Seriously.. the bot should connect there just like the user does and read messages, parse and take action.
Long live IRC =)
BOTs that say stuff works this way: You are on a channel and then all of a sudden a BOT joins and says: "The new release of your website has been successfully updated"
Usually I have met two kinds of people. Those who do not need any motivation to learn new things about computers. And those who will just flat out refuse to learn anything that remotely does not look like what they are already accustomed to.
The biggest "win" for Slack where I worked was getting the non-engineers on it (product, UX, etc), and I doubt they prefer Slack because of the bot writing :)
However Slack does require HTTPS which complicates things, but is also quite a must in current day and age.
I lately only ever use any chat client sporadically so I’m out of touch, but may be needing a platform soon.
Interesting note: I worked at AOL when AIM was introduced and was one of the first users :-P When I moved to tech support of a local cable internet company that was our official work chat :-)
I have no idea what the future holds, and I always welcome new tools and disruptions, and I'm using slack, discord, messenger etc for various communities. What keeps me from leaving irc is:
* friction in moving all users that have been using an IRC channel for 20 years
* stupid stuff in slack and messenger like lock in and slow search. I really like grep:ing logs for links and discussions and then reading the context up and down, which I have found difficult in web services.
Does TheLounge let users upload custom emoji? I ask, because my coworkers say, "You can take Slack from my cold dead hands". There was even a great emoji war.
I would like to stand up a web interface to IRC and let folks play around on it. I tried Convos, but it didn't seem to fit that piece of the puzzle.
For the backend, I have always used UnrealIRCD + Anope services. It has always been rock solid and scales beyond any need I could imagine. It would be great if there were a modern web interface I could put in front of it that people would want to use.
But there is always that irc channel easily to get into and will be there in 20 years.
I know that I can extend my irssi client with plugins needed to preserve history, flag stuff, save in database by triggers, then export that in whatever way I want and serve to the users.
I used to do this anyway so that I could reload the bot without reconnect spam
1) https://github.com/pR0Ps/znc-logsearch
2) https://github.com/robinsmidsrod/znc-log-viewer/blob/master/...
The best apps tend to be platform dependent. I know many who like http://colloquy.info for mac, for example.
Quassel alone is a kinda nice client, with the entire ecosystem around it, it becomes amazingly powerful.
And the beauty of the Qt client is that, being Qt, you can fully style it with css - e.g. https://bugs.quassel-irc.org/projects/quassel-irc/wiki/Style...
Disclaimer: I contribute to some of the above mentioned projects)
I've never tried Glowing Bear. Maybe that would be a nice way for friends to get comfortable with IRC?
Works well, and is a native app that fits well into the general ecosystem.
Most people who use Slack haven't ever used IRC professionally (or at all) - I've shown IRC to people who love Slack and I usually get "Ugh, it looks so old fashioned and difficult to use" as a reaction. Looks matters a lot if you want people to use it - most IRC clients are old or have designs based on old clients.
Plenty of Slack clones out there that look decent that have similar business models. What would be awesome if there's an IRC server that looked and acted like Slack; nice features like:
- a website to log into like Slack (with benefits like modern web design and Github, Twitter, Facebook login). - an irc client that looks decent on website, desktop and phone clients (and doesn't run on electron). - having multiple channels for one company like Slack channels in a group. IRC currently requires you to register several channels (which is annoying).
------------
As for the difficulty in writing bots for Slack vs IRC, sure it's easier to write stuff for Slack because:
- most Slack bots/services are written by companies who want their third party services to be easily integrated into whatever team communication their client use.
- most custom bots are variation of some bots that someone else has written (anecdotal evidence but pretty sure it's true). I'm pretty sure it's not that different for irc.
- most people don't bother writing bots unless they're willing to play around with bots; difficulty isn't an issue when it comes to writing one and I haven't seen bot development treated as an actual task (it's more of a hack that works and isn't really touched again.)
------------
Honestly, this seems to be a case where the author neglects how real-life people work in favor of code "niceness" (for lack of a better term). There's a reason why most people use Microsoft products (and it isn't because they make great software.)