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). 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.) I'm pretty sure it's not that different for irc. most custom bots are variation of some bots that someone else has written (anecdotal evidence but pretty sure it's true). 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. IRC currently requires you to register several channels (which is annoying).Īs for the difficulty in writing bots for Slack vs IRC, sure it's easier to write stuff for Slack because: having multiple channels for one company like Slack channels in a group. an irc client that looks decent on website, desktop and phone clients (and doesn't run on electron). a website to log into like Slack (with benefits like modern web design and Github, Twitter, Facebook login). What would be awesome if there's an IRC server that looked and acted like Slack nice features like: Plenty of Slack clones out there that look decent that have similar business models. Looks matters a lot if you want people to use it - most IRC clients are old or have designs based on old clients. 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.
Not having to deal with different servers & terminology that look scary also helps (a lot) for most people using Slack. I dislike slack (probably because of the culture in Slack groups) but I do think that having a mobile app & ease of use is why Slack is okay. :P)Īs much as I like IRC, I don't get why the author hates slack so much. (Bet you still have to try and explain the difference between http and https to her too, and that always ends with *sigh. Similarly, Email fetching itself has gone through one major protocol shift under her nose without changing the very nature of it, so to make claims that in the particular instance of messaging she should know the protocol is arbitrarily moving the rule-bar. XMPP is the protocol that you're talking about here but you shifted gears midway through to say that she should know what instant messaging is. FTP, IRC, HTTP, and SMTP are all ubiquitious, but not necessarily the most popular method for describing things, keeping in mind that we haven't fully shut the book on the internet = www. You're mixing the ubiquity and common parlance/popularity to suit your situation, but it doesn't work that way. Given that you're describing your Mum in the same fashion we typically all do (And to avoid the "Yes, she's actually very technical" bait-n-switch), we'll assume no.
0 kommentar(er)
