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

441–450 of 730 posts

Re: Slack Is Buying HipChat from Atlassian

#441

Post by wting »

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…

How do non-engineers update documentation?

Re: Slack Is Buying HipChat from Atlassian

#442

Post by [deleted] »

adrianpike wrote: post #362
visualphoenix wrote: post #354

This both sucks and is great. Sucks for me. Hopefully will be great for Mattermost and Matrix. For HIPAA compliant shops Slack is a non-starter. Mattermost will hopefully get a lot of corporate $ now. I wish Matrix's dendrite[0] golang replacement homeserver was finished and in better shape. I'd much prefer to go the Riot/Matrix route, but it doesn't feel ready for prime time yet. HipChat Server was SPOF but could be…

Hey, can you elaborate a touch on the lack of HIPAA compliance with Slack? Some folks on my team seem to think it's compliant - and I'm not finding true hard answers either way (ignoring the BAA side of things)

[deleted]

Re: Slack Is Buying HipChat from Atlassian

#444

Post by kupiakos »

emodendroket wrote: post #286
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…

It seems he is in a different camp, specifically the one where you aren't on a chat application all day

Not directly relevant, but it's possible OP is a girl, so not necessarily "he".

Re: Slack Is Buying HipChat from Atlassian

#445

Post by u801e »

ebiester wrote: post #264
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: Two use cases. With email, how can I subscribe to conversations I'm interested in? Mailing lists are nice, but we have no real way to make mailing lists that start and stop on the fly like a chat channel in a way that is searchable to the entire organization during or after the fact. What email list system allows for quick creation and the ability for everyone in an organization to know that a conversation is…

> With email, how can I subscribe to conversations I'm interested in?

There's always newsgroups, which use NNTP (which isn't that dissimilar to email). They have existing groups in a hierarchy that can be subscribed to. It doesn't really give users the ability to create new newsgroups in the fly though.

Re: Slack Is Buying HipChat from Atlassian

#446

Post by afranchuk »

Jach wrote: post #425
sumedh wrote: post #418

Earlier quoted context omitted.

> 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:).

Nah, it just shows the regex as typed. So not much of a different experience from traditional irc!

Re: Slack Is Buying HipChat from Atlassian

#447

Post by lossolo »

theamk wrote: post #312
lossolo wrote: post #261

Earlier quoted context omitted.

We do not use Slack, we use IRC for direct and fast communication. We do not use it for things that need RFCs and technical specifications, for that we use gitlab and other tools. IRC is great and I am using it for 14+ years already. It's stable, fast, efficient and secure with lots of options. I've written a lot of IRC bots in many languages because protocol is so easy and every language have library/bot for IRC tha…

What is the good story of multi-computer/mobile IRC access, with shared read state notifications? I used to run IRC on the server in the screen session, but this is unusable on mobile. And setting up properly was a total PITA.

You could use znc.

Re: Slack Is Buying HipChat from Atlassian

#448

Post by Diederich »

bigiain wrote: post #349
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.

For one thing, an IRC client doesn't pin a core of my cpu at 100% and consume half a gig of ram... (But I realise I'm well out on the losing end of this argument, even in groups of old-school hard core technical friends/colleagues, I've been given the "crazy look" when suggesting we just use irc for chat... )

> pin a core of my cpu at 100% and consume half a gig of ram...

I'm not doubting you, and I acknowledge that I hear that kind of thing with some frequency, but I've not seen Slack (running in Chrome on Ubuntu) use anything like those amounts of resources.

I've had a pretty busy slack client running for several days, and it's using 204,484K of memory and 2.0% of one CPU.

Re: Slack Is Buying HipChat from Atlassian

#449

Post by rrdharan »

alanfranzoni wrote: post #260
gregmac wrote: post #239

Earlier quoted context omitted.

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…

Your suggestions may work inside a company. E-mail is the only federated system we've left. If you need to contact somebody outside it, you're screwed. XMPP/Jabber could have solved some of this, but it's pretty dead right now.

I think if you ask Slack about that they'll happily tell you about Slack Grid.

EDIT: Whoops actually Shared Channels is the feature I was thinking of: https://slackhq.com/introducing-shared-channels-where-you-ca...

Re: Slack Is Buying HipChat from Atlassian

#450

Post by archildress »

Microsoft Teams isn't successful because it's a great product, it's because their sales team goes into corporate environments where they're already using Office 365 and offer Teams for free as an integrated extension to the rest of the suite.

Big companies aren't choosing between Teams and Slack, they're choosing between Teams and email.

Post reply on HN