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

241–250 of 730 posts

Re: Slack Is Buying HipChat from Atlassian

#241

Post by nwatson »

alienreborn wrote: post #220
core-questions wrote: post #70

Earlier quoted context omitted.

I run the Atlassian stack for my company, so here's some thoughts on this: - Jira is pretty bog-standard these days, huge installed base. It's a bit weird to administer, and not as powerful in many ways as I'd like (especially compared to a more flexible system like ServiceNow). However, it's entrenched and a lot of people like it. - Confluence is a top tier wiki. I actually find it very nice to work with, both from…

Every engineer I met dislikes Confluence. Engineers who write most of the documentation don't like using Confluence which lead to out dated, subpar and incomplete documentation. In my org, I noticed this and created a github repo to push documentation in Markdown. I created initial version of docs and now every engineer in our team uses it because they know markdown, appreciate version controlled docs and can use wha…

I'm an engineer and love Confluence + Gliffy. Writing fully interlinked documentation with illustrations and tables and styling is much easier than with any other tool.

Re: Slack Is Buying HipChat from Atlassian

#242

Post by toomuchtodo »

tomnipotent wrote: post #225
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.

Email is crap for many types of workflows that Slack excels in.

It’s too bad most of those workflows don’t apply to business use cases.

Is it a chat client? A knowledge base? A conference call? A command line? Who knows!

Re: Slack Is Buying HipChat from Atlassian

#244

Post by GuiA »

slededit wrote: post #179
ironjunkie wrote: post #165

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…

A few months ago slack's early plan was posted here. From day one this was the goal - they knew it was just a chat app so they had to make it feel like something different. Its one of the best marketing coups in recent history and I'd love to see more analysis on how it was pulled off.

> Its one of the best marketing coups in recent history and I'd love to see more analysis on how it was pulled off

Steward Butterfield pushed private beta invites to his well connected Silicon Valley social media friends, who then imposed it in their startups because “it’s what everyone else is doing, it’s going to revolutionize communication”. Rinse, repeat.

Source: a social media ninja wizard friend of Butterfield worked in the same startup as I did in the private beta days. I found it to be yet another internal chat app at the time, but my CEO drank the kool aid right away.

Re: Slack Is Buying HipChat from Atlassian

#245

Post by prlambert »

tomnipotent wrote: post #225
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.

Email is crap for many types of workflows that Slack excels in.

I'm curious as to how that breaks down? Which kind of workflows are best in email, which in Slack?

Re: Slack Is Buying HipChat from Atlassian

#247

Post by aaronharnly »

captain_perl wrote: post #198

Just for the record, I surveyed a dozen Hipchat users who used it all day in late 2016 for software development. They had zero complaints about using Hipchat. My opinion of the Hipchat web client at the time was that it worked fine (no complaints from me.) I believe we were on the free tier, so that was a great deal. A new Eng. VP wanted to seem hip, so he switched us to Slack "to ensure we were using the best tools…

Mid-to-late 2016 was the peak of periodic outages in HipChat (like, several hours per week, which is a lot for a core messaging platform), which was when we threw in the towel and switched to Slack.

At the time, Slack had the feature of "you can log in", which teams really liked :)

https://status.hipchat.com/uptime?page=10

Re: Slack Is Buying HipChat from Atlassian

#248

Post by Karunamon »

Walkman wrote: post #166
qabqabaca wrote: post #56

Earlier quoted context omitted.

Out of interest, why would you guys never use a cloud solution? Sensitive conversations? Server reliability?

For example when a company acquires another, your workflows will be broken, you are forced to move and learn the new tool and you have no control over YOUR OWN data at all.

Like when you buy a product that seems solid and then have to scramble to find a replacement because it's being shut down out of nowhere?

--Hipchat onprem user

Re: Slack Is Buying HipChat from Atlassian

#249

Post by ge0rg »

Customers with HipChat installed on their own servers will be able to use it for an extra few months or as long as two years, depending on the version.

Slack and Atlassian will make it easy for customers to move, but they won’t be forced to switch, Butterfield said.

So they are not forced to switch, but if they don't then their chat will cease to work?

Re: Slack Is Buying HipChat from Atlassian

#250

Post by dom96 »

rspeer wrote: post #209
bluedino wrote: post #193

Earlier quoted context omitted.

Persistence can be created the the right proxy/helper and clients

This is a common refrain of IRC users who don't know what it's like to have real, convenient persistence that works for everyone. Nobody has made persistent IRC channels that are as usable as newer chat products that don't try to be IRC.

BNCs provide a semblance of persistence. But the real problem with IRC is smartphone persistence, I think irccloud is the only service that solves this. But alas, it isn't free.

So can this be solved for free? Is it even a good idea to solve it?

Post reply on HN