Live data from Hacker News

Slack Is Buying HipChat from Atlassian

bloomberg.com

151–160 of 730 posts

Re: Slack Is Buying HipChat from Atlassian

#151
post #127

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…

> What are enterprises supposed to use? We run Mattermost on-prem. We've been quite happy with it. They have well-defined [1] migration plans for Slack, Hipchat, and others. [1] https://docs.mattermost.com/administration/migrating.html

"For teams with large amounts of data, the export function has been reported to fail and it may be difficult to reclaim your team’s data. Consider contacting HipChat support to see if a new solution is available."

They're kidding, right? That's a well-defined migration plan?

Re: Slack Is Buying HipChat from Atlassian

#152
post #80

Earlier quoted context omitted.

I mean this without being tongue in cheek, but Teams itself is anti-competitive. It's a horrible product which is basically only in use because it's bundled into Office 365. Absolutely nothing in Teams is not done better in other products, including Microsoft's own products such as Skype for Business or plain old Skype. Business chats in general are just completely incongruent with what users are expecting from end-u…

What about it is horrible? My team loves it.

Same here. We just started using it and everyone really likes it so far. Much better than Skype. I've tried Slack and didn't really care for it. I realize MSFT is mimicking the Slack style in Teams, but I just didn't really actually want to use Slack. But Teams seems like something I want to use.

Re: Slack Is Buying HipChat from Atlassian

#153

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…

Would Keybase Teams fit the bill, with end to end encryption? Or has to be on-prem, even if encrypted, for your requirements?

(I don't have any association with Keybase, I've just investigated this product as a Slack alternative.)

Re: Slack Is Buying HipChat from Atlassian

#154

Earlier quoted context omitted.

What would you recommend instead of Jira?

Phabricator ( https://www.phacility.com/phabricator/ )

I would also recommend this. I've been using it for a while and it's amazing. Tightly integrated into version control, great team/project/task management, code review tools, great command line integration though arcanist.

Re: Slack Is Buying HipChat from Atlassian

#155
Wow. Atlassian is really on the way down, giving up on such an important and strategic part of the business. They've given Stride not even a year to try to compete.

Guess they'll always be the JIRA company. Congrats to Slack to winning the Enterprise Market!

Re: Slack Is Buying HipChat from Atlassian

#156
post #95

Earlier quoted context omitted.

An opinionated workflow of collecting from a development team and its customers potential future efforts, estimates of the cost and value of those efforts, prioritizing based on those estimates (maximize expected value, minimize expected cost), scheduling & forecasting efforts based on a sound statistical model (e.g. estimation error).

You can accomplish most of that with Phabricator[1], except for the forecasting efforts. As for the forecasting; I worked at Amazon which had a dedicated JIRA engineer and that was the best I've ever seen JIRA being run and used. In my time there, I never saw any manager predict anything consistently accurate over the course of a long project with it without actually talking to engineering. JIRA promises armchair man…

JIRA's problem is it's too configurable and popular with folks who are into prescriptive authority, so it absolutely can be worst tool you've ever used, and frequently will be.

Re: Slack Is Buying HipChat from Atlassian

#157
HipChat was a great tool 3 years ago. Atlassian left it to wither on the vine. Really too bad, as I enjoyed its simplicity.

Also, data export is great, sure, but what I really want is someone to re-setup all our build and monitoring notifications in Slack :P

Re: Slack Is Buying HipChat from Atlassian

#159
post #50

Earlier quoted context omitted.

The exact opposite, Atlassian is selling and retreating.

I see it as a step towards integrating more (or in this case better IMO) things into their ecosystem. Consolidating Hipchat with Slack is a step toward that.

Atlassian is selling the defunct Hipchat to Slack.

Re: Slack Is Buying HipChat from Atlassian

#160
post #65

Earlier quoted context omitted.

Yeah, a rare glimpse into how these execs actually think. I'm suprised the pr people let this through their filters.

I agree completely, that's a terrible statement for an executive to make and PR should have stopped that. But on the other hand, I can almost see the logic in it. I'm making a huge leap here, but I remember back in the early 2000s, I had some friends who used AIM. I had some friends who used MSN. I had some friends who used ICQ. I had some friends who used Yahoo. These different chat services were really all exactly…

> I just want all my friends using one so I don't have to sign into fifteen different services just to communicate.

If only the different services would be able to talk with each other, you wouldn’t have to get your friends to all switch to one of them. But, here we are, a decade or two later, and interoperability is still nonexistent.

Post reply on HN