Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack Is Buying HipChat from Atlassian

bloomberg.com

Post reply on HN
Print view View original

551–560 of 730 posts

Re: Slack Is Buying HipChat from Atlassian

#551

Post by sqldba »

halostatue wrote: post #462
mmanfrin wrote: post #196

Earlier 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…

Hipchat actually outperformed Slack for my team in every respect, with three exceptions (all of which were supposed to be solved by Stride): 1. No markdown support and half-assed code highlighting support. 2. No (real) message editing. 3. Silly parenthesis based emoji. Its search is better than Slack’s; its performance is better than Slack’s; its integrations are better than Slack’s; its client memory and CPU usage a…

The lack of Slack on-prem over HipChat is a deal killer for major Enterprise. You can justify "cloud" when Microsoft is running it and has millions of dollars to put into feasibility and security studies and audits.

Letting a strappy upstart have access to that data is a completely different story.

Re: Slack Is Buying HipChat from Atlassian

#552

Post by porker »

karmelapple wrote: post #530
munificent wrote: post #366

Earlier quoted context omitted.

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 never expected that the other party is sitting and staring at the screen in any Slack or chat I’ve used. An @mention will change the expectation of interrupting or not, but as someone who has used various chat programs for 24 years of my life, this ha never been an expectation I’ve had, nor one I’ve seen too frequently expressed. What do you think has caused that expectation in your mind? Do you wish that for…

I've used Slack when contracting at companies (remote and sat in the same room)

> Have you worked with people who do expect that?

Yes. Manager expects it to be like talking to you across the room. You answer there and then. If you slack him though he doesn't expect to reply immediately and gets annoyed if you interrupt him to say you really need an answer.

> Do you wish that for the people you’re chatting with? Yes, saves making a telephone call.

There again, if I Slack someone, it'd better be important not time-wasting.

Re: Slack Is Buying HipChat from Atlassian

#553

Post by locusofself »

jawilson2 wrote: post #258
apple4ever wrote: post #130

Earlier quoted context omitted.

We use Slack now, and are looking to migrate to Mattermost (since we run GitLab already). We don't want to pay the price we'd need to pay to keep Slack, and plus we want to host our own.

We moved from Slack to Mattermost, and Mattermost is garbage. Messages are delivered late (by hours), if ever. You don't get notifications correctly. It takes seconds (more than 10 sometimes) to load a page. Sometimes the page goes blank. Much of our office has reverted to email and phone calls for many things that would have worked fine with Slack.

I run 25+ deployments of mattermost (some free and some enterprise for LDAP support) and don't have those issues on any of my systems. Some features we would love to see arent there, but all the basics work great if your network and configuration is good.

Re: Slack Is Buying HipChat from Atlassian

#554

Post by it33 »

solatic wrote: post #544
it33 wrote: post #509

Earlier quoted context omitted.

Mattermost CEO here. We're thinking of offering a special package for HipChat customers who want to stay on-prem using Mattermost. It's perhaps a mix of services, migration/import assistance and possibly a discount to our commercial version. Would such a package be interesting? For anyone who'd like to discuss outside of HN, please feel free to mail us at info at mattermost.com

Hey, I sent you guys an email - looking forward to hearing from you

Thanks! Got the mail and responded, looking forward to discussing more.

Re: Slack Is Buying HipChat from Atlassian

#555

Post by porker »

gregmac wrote: post #239
philwelch wrote: post #200

Earlier quoted context omitted.

> There are two camps: the we-should-just-use-irc camp, and the we-need-every-feature camp. I'm firmly in the "email should be used for substantive discussions" camp, but ever since we got the bandwidth and CPU necessary for the internet to not be a primarily text-based medium, the illiterates took over and that was the end of that.

I'm firmly in the "email has no place in internal discussions whatsoever" camp. Tasks belong in tickets, long-term documentation/policies/meeting notes/etc belong in shared space (wiki), and discussions are faster and more productive in realtime (in-person, video call, or chat). E-mail might kick some of this off, or be used to schedule, but that should be it. The problem I think most people run into with the realtim…

> The problem I think most people run into with the realtime discussion is failing to document the outcome of the meeting -- and that of course goes into a ticket or long-term docs. A meeting with no notes or outcome might as well have not happened.

I think the attraction of email is it looks like it short-circuits the need for this. "It's all in writing in the email trail" makes moving fast look easy (no realtime meeting that then has to be written up, the document amended on people's feedback etc). But understanding is missing and misunderstanding happens.

I'm starting to move an organisation's planning from emails into meetings and specifications. They are resisting massively because it "wastes" time. Given every project up to now has changed spec twice after launch, I see time being saved if it's correct at launch.

Re: Slack Is Buying HipChat from Atlassian

#556

Post by lloeki »

jawilson2 wrote: post #258
apple4ever wrote: post #130

Earlier quoted context omitted.

We use Slack now, and are looking to migrate to Mattermost (since we run GitLab already). We don't want to pay the price we'd need to pay to keep Slack, and plus we want to host our own.

We moved from Slack to Mattermost, and Mattermost is garbage. Messages are delivered late (by hours), if ever. You don't get notifications correctly. It takes seconds (more than 10 sometimes) to load a page. Sometimes the page goes blank. Much of our office has reverted to email and phone calls for many things that would have worked fine with Slack.

Something seems off in your setup. I've been doing some crazy live database massaging straight from psql and everything has been reflected basically instantly across all Mattermost clients.

Re: Slack Is Buying HipChat from Atlassian

#557

Post by brey »

it33 wrote: post #509
solatic wrote: post #107

Huge problem for on-prem Hipchat customers. Plenty of customers out there not willing to put all their internal communications on the other side of their firewall, and now have to migrate. Slack doesn't have an on-prem option. Microsoft Teams doesn't have an on-prem option. What are enterprises supposed to use, RocketChat? Matrix? With no clear migration path? Really poor move on Atlassian's part. It would be one thi…

Mattermost CEO here. We're thinking of offering a special package for HipChat customers who want to stay on-prem using Mattermost. It's perhaps a mix of services, migration/import assistance and possibly a discount to our commercial version. Would such a package be interesting? For anyone who'd like to discuss outside of HN, please feel free to mail us at info at mattermost.com

Yes, I'd be interested. We're evaluating Slack, MS Teams and Mattermost as a successor to Hipchat.

Something to move the needle commercially in favour of on-premise would be helpful in that evaluation.

Re: Slack Is Buying HipChat from Atlassian

#558

Post by rimliu »

std_throwaway wrote: post #535
solatic wrote: post #107

Huge problem for on-prem Hipchat customers. Plenty of customers out there not willing to put all their internal communications on the other side of their firewall, and now have to migrate. Slack doesn't have an on-prem option. Microsoft Teams doesn't have an on-prem option. What are enterprises supposed to use, RocketChat? Matrix? With no clear migration path? Really poor move on Atlassian's part. It would be one thi…

This shows one strength of open source where you have the option to fork and maintain your own solution in the case the project heads the wrong way. Unfortunately the whole world seems to be heading the wrong way with cloud based "everything as a service" where you control nothing. If the provider or cloud goes down you have nothing. Even if they just take your keys you have nothing. It's quick and easy to setup and…

Forking and managing has a cost associated with it too. If your own DC burns down you also have nothing. There is no "wrong way" just a different ways to evaluate risks-benefits and choosing whatever works best for your case.

Re: Slack Is Buying HipChat from Atlassian

#559

Post by realusername »

inetknght wrote: post #488
capkutay wrote: post #373

Earlier quoted context omitted.

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…

Better than "Skype with a way better UI". * it has a history I can actually search. Skype used to have this, but removed it when they rewrote it in Electron. !@#$ you to whoever at Microsoft decided to get rid of that; I used chat history search every day as part of my workflow. * it has an API/plugin ecosystem. Admittedly, that's a walled garden so it's a double-edged sword. But for businesses that's awesome . Skype…

I could also add to your list that Slack actually works in other platforms than Windows. Yes it's Electron but at least it's guaranteed to work, unlike Skype for Linux or Skype for Mac.

Re: Slack Is Buying HipChat from Atlassian

#560

Post by arendtio »

Arathorn wrote: post #266
ReverseCold wrote: post #236

Earlier quoted context omitted.

The matrix homeserver is... suboptimal. I'm running it for a personal instance (two users), and it's using insane amounts of RAM (4-8 GB) and still managing to lag (even though I gave it 4 cores on a Ryzen 2700X). Forget talking in a matrix.org room, even talking to people on other personal/single user servers isn't fully stable. There is a replacement homeserver ( https://github.com/matrix-org/dendrite ) but it's no…

Disclosure: i work on Matrix. We're basically doing nothing but fixing Synapse's performance problems currently, and improvements are on the horizon. We're late because we got sidetracked fixing flaws in the protocol, but as of the last few weeks we're back on perf again. So far we've sped up /sync by 2x and reduced CPU by about 20%, but the RAM improvements should land over the coming weeks unless we have further di…

Why is you current solution so ressource hungry?

I mean, my 10-active-users off-the-shelf XMPP server (ejabberd) uses about 100MB RAM currently.

Post reply on HN