31–40 of 499 posts
Main problem with IRC is that it's not "always on" and I really need this feature. Sure you can use IRCCloud or SSH/Screen into a server, but they both cost money while Slack is free.
How is Slack free? You have to pay per user or apply for an exemption if you are a non-profit. IRCCloud is free by default and you only pay to unlock some extra features. https://slack.com/pricing https://www.irccloud.com/pricing
Replace svn by irc and bitkeeper with slack. Figure out the rest.
However, I am 25 and largely missed the boat on irc. I decided to start using it ~1 year ago. It is hard to use, but we will look at that in a minute. Often, we assume people have as clear an idea of what we are talking about as we do. That is often not the case. Let's explore IRC now.
* Integration has never been a problem ... build bots.
I feel silly and naive, should I know how to set this up? Maybe it is really easy and well documented, and I am an edge case here, but i don't know how to do this. I clicked 3 buttons to setup github for slack. It was very easy and I didn't haystack through building a solution to something that exists. Scope creep on tooling is dangerous as an aside. Thos takes that off the table.
* persistence
again, I have to set up an alternate tool to download the content. i assume this would backup the whole channel so any user could reference it, but it comes by default for free with slack. if each user must have a seperate tool, or go to a seperate place to see a conversation (which may be less searchable) it adds friction.
* code snippets
actually super reasonable to use pastebin. slack is at least as annoying for code as pastebin, if not more.
* etc
The point is, not everyone lnows as much as the author about IRC who is likely quite a talented developer who grew up on it. An 18 year old likely won't have used irc as much as older generations given the plethora of tools and chat clients.
FOSS is a choice and a philosophy and that should be given some degree of consideration. Utility, workflow and getting new devs onboard and contributing is important. I agree with the author that it bears consideration, but slack or hipchat are much easier than IRC.
Earlier quoted context omitted.
There are lots of web-based IRC clients out there
Which is part of the problem. People don't want "a lot of web-based IRC clients", they want only one and it has to be amazing.
Main problem with IRC is that it's not "always on" and I really need this feature. Sure you can use IRCCloud or SSH/Screen into a server, but they both cost money while Slack is free.
How is Slack free? You have to pay per user or apply for an exemption if you are a non-profit. IRCCloud is free by default and you only pay to unlock some extra features. https://slack.com/pricing https://www.irccloud.com/pricing
If IRC's limitations are too cumbersome to workaround there is also XMPP.
Previous discussion on this: https://news.ycombinator.com/item?id=10280611
> Problems with IRC that Slack solves Main thing that Slack solves as far as I'm concerned is a great and uniform client on every platform. Don't get me wrong, I love irc. This is where I started learning everything I know about computer. I tried many times to get various team on it and it always failed. I think it's mainly because the learning curve is too big for non-technical/busy people, and that there's no good…
I think it's mainly because the learning curve is too big for non-technical/busy people Really? Does using Slack not require opening a client application and logging in, like just about every other realtime messaging platform? I know many "non-technical" people who use IRC.
I love IRC and grew up with it. But don't compare it to Slack for technical knowledge requirement.
I.e. does IRC or any IRC client support sent, received, read confirmation the way that What'sApp or Google Hangouts reports this information?
It is reasonable to raise the point that building FOSS software while using a closed piece of software as a core tool bears consideration. However, I am 25 and largely missed the boat on irc. I decided to start using it ~1 year ago. It is hard to use, but we will look at that in a minute. Often, we assume people have as clear an idea of what we are talking about as we do. That is often not the case. Let's explore IRC…
Instead of using slack, use IRC Cloud.
That's how I felt during the dot bomb era when I heard that General Electric had been eclipsed in market cap by one of the new startups, Amazon.
Although IRC has an old heritage, it's arcane and user-hostile. To some extent it wants to be that way, to help keep the unwashed masses away.
IRC isn't as easy to use as Slack for things like persistent history accessible from mobile and desktop, and integration to git. That's why alternatives are gaining ground.
If this situation bothers you ideologically, there's actually something you can do! You can help open source alternatives be as easy to use and integrate as Slack is. If your goals are less ideological and you just want your team to immediately get on the task of solving business problems, consider Slack.