I really didn't like Stride but couldn't put my finger on why not. A lot of shortcuts from Hipchat didn't migrate across but I could live with that, something just felt off...
Slack Is Buying HipChat from Atlassian
381–390 of 730 posts
Re: Slack Is Buying HipChat from Atlassian
#382"Taking out a competitor is good for Slack, There’s fewer choices for people.” - Stewart Butterfield in the above article.
When are tech CEO's going to realize it's bad to sound like a monopolist b/c anti-trust?
I tend to agree with Ben Thompson of Stratechery that one of the best ways to thwart emerging monopolies and preserve choice for consumers it to prevent companies from acquiring competitors. Although today Microsoft is the goliath and Slack is the david, in today's world David's grow up very very fast...
Re: Slack Is Buying HipChat from Atlassian
#383Earlier quoted context omitted.
IRCv3 has some great features it’s trying to standardize: https://ircv3.net
Mean while, every single chat and IM application has steamrolled straight past.
I think ‘steamrolled’ is a little strong. Slack is more or less a pretty design on otherwise old concepts and ideas. Not to trivialize that: it was despirately needed.
Really IRC just needs some well designed clients, I don’t like any of the offerings I’ve seen for iOS or desktop.
Re: Slack Is Buying HipChat from Atlassian
#384Earlier quoted context omitted.
You're in the mute-everything-non-critical class, which is a good practice regardless of the client. If they really need you, they'll ring/call/DM. Otherwise, you can check it whenever you're ready.
I think you're confusing communication throughput with latency. I also don't like using chat at work. It's not because I want less interaction , it's because I want less interruption . Email has a norm of asynchrony where I can respond to email when I reach a good point in my current task. With chat, the other party is presumed to be sitting staring at the screen waiting for my reply, so I have to drop what I'm doing…
I have a different expectation while using Slack. I agree that enough people have your expectation that it's something that should be discussed and agreed upon by everyone using the 'chat' system... Slack provides an easy @channel and @everyone mechanism to control notifications.
Re: Slack Is Buying HipChat from Atlassian
#385Earlier quoted context omitted.
There are two camps: the we-should-just-use-irc camp, and the we-need-every-feature camp. You fall in to the former, and I would bet that a lot of people here fall in to the former. However, many people fall in to the latter, and Slack handily beats the competition there. There is also an element of having nice and polished features baked in that appeals to many people. Want it on your phone? There's an app. Want to…
When was the last time you used Linux? I installed Ubuntu on a Dell lappy provided by work, everything just worked and it required less tweaking than osx would have for serious SWE work.
I heard the same luring song for the last 20 or so years.
If Linux works for you then enjoy it.
Don’t even try to suggest that Linux is easier than Mac OS X because I don’t like liars.
Re: Slack Is Buying HipChat from Atlassian
#386I haven't used Stride, but some of the features it was touting that Slack doesn't have seemed nice. I liked the idea of marking something as a "decision". Not sure how that played out in practice, but I know I'm constantly searching our Slack conversations at work to try to find decision points. Would be cool if they integrated that, and other features from Stride.
Re: Slack Is Buying HipChat from Atlassian
#387Earlier quoted context omitted.
HipChat had some major uptime issues. I have friends who experienced whole day outages at their companies. I hear a lot of people on HN say it was "Just IRC" and I'm always surprised by that. If IRC was so compelling then why didn't it take off? Why did Slack have a meteoric rise? It can't be for no good reason. I think the answer is that the interface fluff they added is actually extremely important and valuable. Th…
My Linux user group used to hangout in IRC until 3 or 4 years ago when little by little we stopped joining the channel. Some of us tried IRC clients for smartphone and it was a lousy experience. Until one day someone created a Telegram group. Now we are all there, the conversation might not be as fluid as IRC, each is in their own timezone, but it is there.
Yes, IRC I think finally "failed" once persistence went from "nice to have" to "need to have" feature. Yes, you can work around this if you are a top 20% techie who enjoys that stuff, but most don't.
Mobile basically made the "all clients synced from anywhere" a necessity, and then lack of IRC client development for things like rich media hurt to boot.
Re: Slack Is Buying HipChat from Atlassian
#388Earlier quoted context omitted.
You're in the mute-everything-non-critical class, which is a good practice regardless of the client. If they really need you, they'll ring/call/DM. Otherwise, you can check it whenever you're ready.
I think you're confusing communication throughput with latency. I also don't like using chat at work. It's not because I want less interaction , it's because I want less interruption . Email has a norm of asynchrony where I can respond to email when I reach a good point in my current task. With chat, the other party is presumed to be sitting staring at the screen waiting for my reply, so I have to drop what I'm doing…
I completely agree. It is also the effort to interruption ratio that has reached a tipping point. Once upon a time if I wanted someone's help right now i would have to walk to the actual desk, and bribe them with caffeine or chocolate. If the effort of levering myself out of my chair was greater than the benefit to me I stayed put - hence interrupting another person had a minimum price point - the other person may not like it but the price was paid in public and there was a perceived value to the business.
Phones reduced that price point - but it still has a cost to me.
Now IM / Slack has flipped it on its head - the cost to the interruptor is negligible but the cost for the interruptee is their mental derailment - and no ability to judge the overall benefit of helping until it is too late
Plus I don't really see the win - for real time co-ordination it's hard to beat a mass phone conference ( we are doing a complex release with phased rollouts and devops watching the traffic - then get your headsets on, and everyone must hurry up and wait)
Slack is just secondary for that - useful for spelling out what has been said but otherwise ...
For letting others know what has happened - that's called an after the fact report or "email".
So really i don't see the use case except it means that when like the phone, i reach you i am confident of a reply in a given time period - that may well be defining facto
Re: Slack Is Buying HipChat from Atlassian
#389Earlier quoted context omitted.
I read this as HipChat’s own export function having problems handling large amounts of data. I’m not sure how this is Mattermost’s fault.
I'm not sure what they mean by "export function". Hipchat isn't "an application", it's a bunch of services running on a network of VMs. At the very least, Hipchat includes Elasticsearch and MySQL. Seems odd that they'd rely on any particular Hipchat API when they can rip that data out of the guts of the machine.
I'm sure there's a fair amount of business logic between what's in the database and what's delivered to the presentation layer. Pulling from a database means that the new company has to reverse engineer Hipchat's API implementation.
Re: Slack Is Buying HipChat from Atlassian
#390Earlier quoted context omitted.
If you want secure emails use GPG. Unlike slack, GPG is both open-source and offers government-level security. I don't think slack is more secure than GPG.
And how does that work for your average person using outlook / google for email?
Then build on top of email, instead of developing yet another 'secure' proprietary system.