Live data from Hacker News

Salesforce Signs Definitive Agreement to Acquire Slack

salesforce.com

411–420 of 659 posts

Re: Salesforce Signs Definitive Agreement to Acquire Slack

#411

I can't possibly see this going well for salesforce. Buying slack for 70x revenue is insane. Their entire market is going to be eaten by teams and google chat, if it hasn't already. Microsoft has such a gigantic advantage when it comes to enterprise productivity software because everyone is already using office. And those that aren't are on g-suite. Slack's recent guidance was horrible too.

Of all the messengers I've used Chat is by far the worst. Especially threading is almost unusable.

How can it be worse than threading on slack?

Re: Salesforce Signs Definitive Agreement to Acquire Slack

#412

Earlier quoted context omitted.

I had forgotten that they bought Heroku. As far as I know, Heroku is still as cool as when I used to frequently use it. Time will tell how it goes with the Slack acquisition.

Aside from it being absurdly expensive and understaffed for support and CS. I mostly agree.

Client services?

Re: Salesforce Signs Definitive Agreement to Acquire Slack

#413

Earlier quoted context omitted.

The video meetings are easily the worst part of Slack. Even though Slack meetings are free and integrated, everyone at my org still uses Zoom with Slack instead.

Are the video meetings worse than chat threading?

They don't work at all in Firefox, so... for any Firefox users, yes.

Re: Salesforce Signs Definitive Agreement to Acquire Slack

#414

Earlier quoted context omitted.

Slack never really fulfilled its promise as a stand-alone company, so not sure what you’re afraid of now. Very unreliable at times eg latency, missed out of video calling, did not take advantage of WFH boom at all, document search was bad.

I don't know if I'd agree that it never fulfilled its promise. It's got a lot of market share and its core product - text chat and messaging - remains pretty solid, despite some missteps. I haven't had that level of unreliability issue with text, though I _definitely_ have with calls. I would agree that Slack had an opportunity to compete with Zoom and others because of COVID that it seems to have relatively squander…

Zoom clients can turn off receiving video, even in browser

Re: Salesforce Signs Definitive Agreement to Acquire Slack

#415
post #53
post #14

I'm somewhat surprised that Amazon didn't end up acquiring Slack, considering that the major thing they are missing compared to Microsoft is productivity tools. If they had purchased Dropbox and Slack they could've gotten a foothold rather quickly and slowed down one of Microsoft's major selling points (you already use Office, why not Azure?). Discord could be another interesting company in the chat space, as I'm sur…

>Yes, I know Chime exists. But I don't think I've ever heard of anyone using it, and Slack is still rather popular. I think even Amazon realized how awful Chime is, given that they, as a company, switched to Slack just a few months ago.

Chime is a great video call system, but wouldn't try for anything more. We're using slack, but still prefer chime for conferences.

Re: Salesforce Signs Definitive Agreement to Acquire Slack

#417
post #110

Eh people will be salty about the Salesforce name but honestly their acquisition of Heroku hasn't caused me any pains regarding our experience with that platform. I'm as skeptical as anyone else, and I think there's more risk in a tighter "integration" making it a miserable experience. Might be a good time in the market for a new Slack competitor!

Wonder what's going to happen to free tier. Some integration into core Salesforce might make sense for reps / teams. Another useful product might be live chats based on Slack tech. Seems good fit, but I do wonder how well they are going to integrate.

maybe free tier was never sustainable and was only a tactic to increase user volume and thus increase Heroku valuation towards an acquisition.

Re: Salesforce Signs Definitive Agreement to Acquire Slack

#418

Earlier quoted context omitted.

Threads are by far the worst part of using Slack. A few coworkers use them, but most do not use them. It causes lots of unnecessary clicking and keeping track of an additional place where conversation is happening.

Worse than getting a million notifications about something you're not interested in yet don't want to mute the channel?

If it's off-topic, IRC's ancient solution has always been "Take it to #channel-cafe" or whatever, perhaps a topic-specific channel. Just /join it, if it doesn't exist it gets created. Or perhaps have a 1-1. But because this affects everyone, it's easy to make it the culture to not spam irrelevant stuff in the main channel, making it a non-problem that threads could alleviate.

In practice you're going to get violators, but that happens with Slack as well. In part because Slack's thread UI sucks so occasionally you'll wake up and see a couple people in after-hours last night who just didn't care and filled up 50-100 messages on the unthreaded channel, forcing people to skim through it or if they were foolish enough to leave notifications on after-hours to get all these pings.

One nice thing basically all modern chat systems have is easy group chat, so you don't have to create a new room, but rooms are nice too. e.g. any time we had a customer case requiring a few people to look into it, we'd just create a slack channel for it instead of using threads on the team channel. After a while someone would archive the channel.

Then there are people who use threads and occasionally click the "send to whole room" option which really screws up notifications. You're looking at it right there in the main team chat, but you have to open the thread or your notifications to dismiss the notification.

Next time I'm forced to use Slack I'll use Ripcord. You know what UI I miss most and would help Slack/Discord/Element tremendously? Tabs.

Re: Salesforce Signs Definitive Agreement to Acquire Slack

#419
post #110

Eh people will be salty about the Salesforce name but honestly their acquisition of Heroku hasn't caused me any pains regarding our experience with that platform. I'm as skeptical as anyone else, and I think there's more risk in a tighter "integration" making it a miserable experience. Might be a good time in the market for a new Slack competitor!

I don't believe Salesforce got much value out of Heroku however. Their main app isn't built on top of it, and they were shopping around for cloud providers to expand to places like Australia.

Re: Salesforce Signs Definitive Agreement to Acquire Slack

#420
post #317

Earlier quoted context omitted.

Haha, it reminds me a bit of Microsoft Account, MSA, Windows Live ID, Microsoft Passport, .NET Passport, and Microsoft Passport Network.

Does it? It's not a good comparison. All of those are brand names for a product still offered with continuity of teams between them and while some of the brand names signaled breaks in compatibility for developers using the services, it was still ostensibly the same product. Whereas most of these Google projects were ostensibly entirely different teams with different project goals building externally similar projects…

So for a 1:1 comparison, let's consider the apps that MS has made in this space over the years. Ignoring the semi-annual rebrands and the MS chat products that were killed from before Google even existed (there's surprisingly many!), there's at least:

1. MSN Messenger (+ rebrands)

2. Skype

3. NetMeeting

4. Lync (+ rebrands)

5. Yammer

6. Kaizala

7. Teams

8. SharedView

9. Windows Meeting Space

10. Groove

11. Qik

I tried to err on the side of assuming that any time they killed one product and immediately replaced it with another, it was a rebrand. (E.g. were Office Communicator / Office Live Meeting / Lync / Skype for Business actually compatible? If not, they clearly weren't just rebrands.)

Overall this seems like a very similar amount of churn, product overlap, and politics-driven product management.

Post reply on HN