3 ms·
More like nobody bothered to make a decent product that could do all the nice things slack is doing. (although, that's not technically true since irccloud does
by dijit 7y ago
More like nobody bothered to make a decent product that could do all the nice things slack is doing.
(although, that's not technically true since irccloud does all the things you just mentioned)
- josteink 7y ago> nobody bothered to make a decent product that could do all the nice things slack is doing. Slack is a closed-source for-profit SaaS, ruled by a single benevolent company. IRC is an open protocol-specification with a multitude of clients, servers and networks. You couldn’t find better apples and oranges for comparison if you tried.
- dijit 7y agoI agree completely. But we're talking about reasons people ended up choosing slack over something like IRC (or, really, any open protocol instant messaging specification). The grand-parent comment raises good points, people want these things, being connected and reachable while not being connected to the server with any client and having a context later on. These are problems that can be solved but nobody has put effort into making a sexy product to do it. (and monetising that kind of product might be troublesome)
- josteink 7y ago> nobody has put effort into making a sexy product Again we are comparing a product to a protocol. I’m just pointing out that this is not a reasonable comparison. There were multiple web-enabled IRC bouncers (closed products) which would be easy to use for anyone, including non-techsavy people. But evidently the majority of IRC-users were fine without that and preferred the traditional client-server-protocol realm.
- dijit 7y agoIRC is more than a protocol, it’s an ecosystem. You cannot simply talk about IRC in complete isolation. It’s akin to comparing SMTP with chrome. You have to include the clients and surrounding infrastructure.
- robjan 7y agoYes, and there was plenty of opportunity for someone to develop a client that scratches all of those itches. But they didn't.
- rakoo 7y ago> (although, that's not technically true since irccloud does all the things you just mentioned) Yes but then you're not using IRC, you're using IRCCloud. Its features are independent from the backend that is used; they could switch to Matrix or XMPP or a proprietary protocol for that matter, and the features would still be there. You can't expect the one you talk to to have IRCCloud and tell them "just search in the conversation history, it's there" because the protocol doesn't allow it. The GP's answer is correct, Slack does a lot of useful things by default. That's why people like installing Ubuntu or even Debian but don't want to take time to setup an Archlinux or a Gentoo anymore: it's fun, but if I just want to do something other than tuning my install I'm not going to consider those distributions. Now, the question is, does that mean that LFS or any bare distribution "lost" to, say, Fedora ? No, because they are meant for different needs. I'd say it's the same for IRC: it's best suited for people who are not interested in the full history and want to talk to people in a synchronous manner, people for whom text is a more than good enough solution and aren't necessarily interested in binary exchanges, people who like pseudonymity, etc
- dijit 7y agoWeird distinction. There’s no difference from this over using weechat relay.
- rakoo 7y agoThe client -> relay protocol for weechat relay is not the same as the client -> ircccloud protocol for irccloud, and both of those are _not_ IRC All those clutches exist to support the deficiencies of IRC, which only proves the initial point: IRC in its current form doesn't do enough, and that's why Slack, with all of those features out-of-the-box, "won".
- dijit 7y agoWhat I was eluding to was that irc (as a server to server protocol) is fine. As a client it has deficits but those are quite literally smoothed over by websocket capable bouncers and weechat relay. IRC The protocol is not competing with slack. The IRC ecosystem is. And yes, it lost.