Hacker News Reader

Comment by ezst | Hacker News Reader

> Some use cases like business chat actually can't have E2EE, and that'd probably be Jabber's foot in the door because no other open solution has taken off in business

So, Cisco Jabber (now Webex)? You can't really compete against Microsoft and its bundling strategy. Even Slack is dying, unfortunately.

View on HN

Yes, you can't beat Microsoft at this, at best you can be a choice for those who want in-house instead of trusting Microsoft.

Webex can't be run on-prem, can it? I vaguely know about the old Cisco Jabber.

If Slack is dying, what's replacing it?

Teams. Your CFO keeps telling your head of Projects/Engineering that he's already paying for it anyway. And your helpdesk loves it because it's sharepoint all the way down and up, and they can shine their "Microsoft Certified Kung-Fu level Sharepoint Master Accreditee" certification.

Our helpdesk doesn't use Sharepoint though :) And we're a Google Apps company, so we don't even have a M365 subscription.

But you're right, the best competitive advantage of Teams is that it's "free"[0]. But that's about it, it's objectively bad in all other ways - anyone claiming otherwise has Stockholm syndrome and is in denial =)

Just the fact that, as a consultant, it's literally impossible to connect to multiple teams workspaces with the same client. The OFFICIAL Microsoft advice is to use Private Browsing in separate browsers...

Meanwhile on Slack I can just hit cmd-number and swap between clients. AND we can have shared channels over instances, like $vendor having a support channel on our Slack with their actual people with their own accounts.

[0] If you have M365 anyway.

MS Teams is terrible, and yet it's gotten this far. I don't know if Slack or Teams is winning, just that Jabber won't beat Teams at its own game.

Thankfully we use Slack where I work. The cross-org channels are cool.

Reply on news.ycombinator.com