I don't see any compelling reason to adopt IRC. It does nothing that I care about that Slack doesn't do. If Slack completely implodes, I would search for Slack alternative. If IRC really was my only option, I'd use it just long enough to write a basic alternative myself that replaced or extended IRC w/ the features I really want.
For one thing, an IRC client doesn't pin a core of my cpu at 100% and consume half a gig of ram... (But I realise I'm well out on the losing end of this argument, even in groups of old-school hard core technical friends/colleagues, I've been given the "crazy look" when suggesting we just use irc for chat... )
I had this problem with Slack. I switched to using it within Chrome. I can't be sure why it performs so much better that way (Chrome throttling it?), but it does.
When is this overhype for Slack going to stop? It is a chat application with a slightly improved UI like it existed 30 years ago. This is a step in corporate IT that I really cannot fully understand. It seems that every company//startup has to use slack nowadays to pretend to be cool again. Everytime I have a serious conversation about the productivity gains or losses of Slack though, it is pretty clear to me that it…
Those aren't slack problems, those are people problems. I can just as easily point to email threads that are incoherent and hard to follow. I can also point to meetings with no agenda that waste everyones time but give the appearance of 'managing' or team building. When used properly (not lazily), Slack is a great place to organize communication between teams. At worst its Skype with a way better UI...what's wrong wi…
Most people are too arrogant to communicate asynchronously successfully. People think that chat is like being on a telephone or in person and that they can demand one's full, exclusive attention. That is some serious arrogance bordering on narcissism when done in personal conversations. At work, it could me more tolerable, but the downside is that no work gets done. Managers need to start to understand this. If you keep someone's full attention for eight hours a day, you should expect no progress. Of course, managers don't understand this either because they are like everyone else described above. In some places, this is understood. I often go days with only a few slack messages at my work, so it's hardly impossible. Then again, we are a fully remote, async business. If I'm not responding, it's rude to demand that I respond, except for pre-scheduled meetings. Not even for emergencies like servers being down. If you have something urgent, call. If not, wait. It's very simple. It works great.
I'm guessing it's highly likely that one of the reasons for the acquisition is to make Hipchat the on-prem version of Slack, or at least create a path to that goal. Why does everyone here assume they will shutter the product? Slack has been promising self-hosted chat for years.
HipChat is known for having a problematic low-level protocol (based on a fork of XMPP), it's featureset is much more limited than Slack's, and it's implemented in a different programming language. It'd be a lot less work to fork Slack and make it work on-premise than do something with HipChat. And that's saying a lot: forking Slack to make it run well on-premise would likely be an enormous project.
Or they could just leave it as is or rebrand it as Slack enterprise until they build a new version based on Slack.
I don't see any compelling reason to adopt IRC. It does nothing that I care about that Slack doesn't do. If Slack completely implodes, I would search for Slack alternative. If IRC really was my only option, I'd use it just long enough to write a basic alternative myself that replaced or extended IRC w/ the features I really want.
I don't see any compelling reason to adopt Slack. It does nothing that I care about that IRC doesn't do. If IRC completely implodes, I would run my own IRC server.
IRC is horrible on phones (shitty history when you drop out of an internet connection, no cross-device unread-count synchronization, no encryption or login, etc). There are add-ons that try to fix that, but it's still a giant pain.
I personally love Riot and Matrix as a "modern IRC".
HipChat is known for having a problematic low-level protocol (based on a fork of XMPP), it's featureset is much more limited than Slack's, and it's implemented in a different programming language. It'd be a lot less work to fork Slack and make it work on-premise than do something with HipChat. And that's saying a lot: forking Slack to make it run well on-premise would likely be an enormous project.
Or they could just leave it as is or rebrand it as Slack enterprise until they build a new version based on Slack.
the UI/UX is so different I'd be very surprised if they managed that
I don't see any compelling reason to adopt IRC. It does nothing that I care about that Slack doesn't do. If Slack completely implodes, I would search for Slack alternative. If IRC really was my only option, I'd use it just long enough to write a basic alternative myself that replaced or extended IRC w/ the features I really want.
For one thing, an IRC client doesn't pin a core of my cpu at 100% and consume half a gig of ram... (But I realise I'm well out on the losing end of this argument, even in groups of old-school hard core technical friends/colleagues, I've been given the "crazy look" when suggesting we just use irc for chat... )
If I had an irc server/service were I could easily login/control access with a Google domain account... <3
One of the things that have surprised me is the lack of a good slack alternative from one of the large companies like Microsoft or Google.
Now, before someone tells me about Teams and Hangouts, they need to realise that Slack/Teams/Hangouts all are glorified Yahoo! messengers but slack is the only one that seems to have a sweet spot where people are comfortable using it.
When is this overhype for Slack going to stop? It is a chat application with a slightly improved UI like it existed 30 years ago. This is a step in corporate IT that I really cannot fully understand. It seems that every company//startup has to use slack nowadays to pretend to be cool again. Everytime I have a serious conversation about the productivity gains or losses of Slack though, it is pretty clear to me that it…
Going through all of your channels you don't need immediate updates from and doing /mute will go a long way to getting the silence you want. People can still @mention you to get your attention if needed. You can check muted channels on your own time when you feel like it. You should also set up Do not Disturb and turn off the red notification dots. The rest is a cultural problem that exists will all communication cha…
Oh my God, people use Slack without changing the "Notify me about" setting to "Direct messages, mentions, and keywords"? I work on a 100% remote team and would rapidly go insane without that.