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

421–430 of 730 posts

Re: Slack Is Buying HipChat from Atlassian

#421

Post by sytse »

qznc wrote: post #109
andreineculau wrote: post #77

Earlier quoted context omitted.

Stick to github issues or similar. Whatever is closer to the real work and gives you the biggest bang for the buck. Not the most wet dream. You do not need a gazillion of workflows and checks and stories and epics and boards etc. "Keep it simple, stupid"

What I like is to specify dependencies. Unfortunately, the simple ones (Github, Gitlab, Trac) don't have that feature. The Jira we use at work has gone overboard. There is too many ways to specify and people are confused. For example, we have "blocks" (B cannot be finished without A closed) and "follows" (B cannot be started without A closed).

As a first step GitLab has implemented relationships in issues, for more context see https://gitlab.com/gitlab-org/gitlab-ce/issues/4058

Re: Slack Is Buying HipChat from Atlassian

#422

Post by spookthesunset »

blkhawk wrote: post #348
amorphid wrote: post #283

Earlier quoted context omitted.

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.

> I would run my own IRC server

That's nice for you personally, but how does running an inhouse bespoke IRC server have anything to do with whatever line of business your company is in?

Re: Slack Is Buying HipChat from Atlassian

#423

Post by hakfoo »

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…

I like the message board model, like Basecamp, myself.

* You can respond in a delayed manner and not appear rude.

* Complex stuff can be previewed before submission.

* The subject and thread organization adds more fine-grained control than you usually get with Slack channels. The #team-name channel might have discussions on several topics at once, not all of which affect you, and no easy way to filter them. On a message board, it's easy to break out a new thread even if people are subscribed to it by default.

* Slack search is ugly because you come back two months later and have to pull the info out of a tangled discussion with unrelated stuff in the middle.

Re: Slack Is Buying HipChat from Atlassian

#424

Post by Jach »

emodendroket wrote: post #294
wuliwong wrote: post #265

Earlier quoted context omitted.

I don't think I've ever used HipChat. What don't you guys like about it?

I worked at a place where employees lobbied for Slack endlessly until we got rid of HipChat because -- and I am being completely serious here -- you can't upload as many custom smilies in HipChat.

On the other hand you have to manually resize things for Slack, whereas Hipchat would autoscale and let you crop too. So annoying.~

Re: Slack Is Buying HipChat from Atlassian

#425

Post by Jach »

sumedh wrote: post #418
wuliwong wrote: post #265

Earlier quoted context omitted.

I don't think I've ever used HipChat. What don't you guys like about it?

> What don't you guys like about it? You cannot edit comments in Hipchat. I can talk about other issues as well but not editing comments is a deal breaker for me.

Sure you can, though I stumbled on it. Type s/sub/repl and it edits.

HipChat works with Pidgin, which doesn't support edits, I imagine you'll see something similar as with the Discord edit feature when you're connected via Pidgin (you get a new message, prefixed with EDIT:).

Re: Slack Is Buying HipChat from Atlassian

#426

Post by Benjamin_Dobell »

munificent wrote: post #366
eganist wrote: post #344

Earlier 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 find clients tend to call to ask "a quick question", this is very disruptive. My experience is if they can't be bothered putting it in writing, then it's probably not very important.

Re: Slack Is Buying HipChat from Atlassian

#427

Post by SamWhited »

jmalicki wrote: post #252
mehblahwhatevs wrote: post #3

> Taking out a competitor is good for Slack, said Butterfield: “There’s fewer choices for people.” Strange quote.

Why is that strange? It's very well established that people hate choices (regardless of what they may say) when you actually measure it: https://sheenaiyengar.com/the-art-of-choosing/ And it's very good for the company, as they don't need to do as much competition with HipChat so they can slow down innovation and raise prices. Win, win.

It's true that individually most people are happier without a choice, but when you take them away you end up cutting out whole chunks of people. What if the thing that went away was accessible to people with certain types of disabilities and the new thing isn't? What if the old one wasn't a public company but the new thing is and now they have to comply with U.S. export laws and you were perfectly okay using it in Iran before but now can't? etc. There are a number of cases where most people won't want a choice, but by giving them what they want and removing one you hurt a lot of other people.

Re: Slack Is Buying HipChat from Atlassian

#428

Post by anant90 »

andrewla wrote: post #94

They changed the headline to "Slack Is Buying HipChat" from "Slack and Atlassian Team Up to Take on Microsoft in Chat Software". The latter still survives in the URL. The "team up" makes it sound ridiculous, like some sort of cabal is being formed -- the team up here is like when I team up with a cheeseburger to take on hunger.

+1 for the cheeseburger analogy. I'll be using it. Thanks!

Re: Slack Is Buying HipChat from Atlassian

#429

Post by KamBha »

We have been using Stride for a few months and are baffled by how bad it can be and how it seems to miss key features that was in Hipchat (such as a call indicator). I used to always say "this is not the hard part of your job, stride " because it would fail to do basic things such as display images.

A colleague of mine found a security issue but had a hard time logging it and had to make it public.

Basically, I got the impression that the stride team in Atlassian was a bit of a mess.

All that said, it is sad to see it go because it was an alternative to the near monopoly of Slack. The only other alternative is rocket chat and MS teams now.

Re: Slack Is Buying HipChat from Atlassian

#430

Post by Jach »

briandear wrote: post #282
wuliwong wrote: post #265

Earlier quoted context omitted.

I don't think I've ever used HipChat. What don't you guys like about it?

Sync. I have three computers and an iPhone. If I check a message on one device, it still shows unread on the other devices. It's total crap.

To be fair Slack doesn't do this and other network related things much better (in my experience). For each complaint here about HipChat I experience the same failings in Slack, just less often. But Slack is a bit better, so people make the argument that it adds up. (We moved from HipChat to Slack several month sago, I didn't find it much of a game changer apart from getting the company to pay Slack to store history and make it searchable but I'm someone who would be content with IRC and searching local logs.)
Post reply on HN