101–110 of 349 posts
Earlier quoted context omitted.
> I thought Google might do this after not buying Slack They did: Google Chat. It’s bundled with Google Workspace.
And it's worse than Teams
I'm more interested in the fact that disclaimer at the top makes me think the entire article is written by AI as a summary of a bunch of reddit posts and tweets and discord topics? Is that what the top says?
> Microsoft did, and Teams is by all reports a solid success. Not sure if the author has used Teams. But otherwise, I agree we need an actual good, adorable Slack clone. I thought Google might do this after not buying Slack, but I'm not hearing anything about their solution.
Slack started with an aggressive "bottom up" approach, they made something actually good and got to worrying about the sales part later. You don't need sales as much when companies come to you, begging you for an actual contract that fulfills their enterprise requirements, knowing that rooting you out is almost impossible.
Teams went the other way, in typical Microsoft style. Microsoft sells it bundled with all the other Microsoft things it sells. Most companies want a Microsoft contract anyway, and have an established sales relationship with MS, so adopting Teams is a lot less compliance, integration and procurement work than adopting anything else. You don't need good UI if your sales strategy isn't predicated on users choosing you for UI.
And then there's Discord, which really isn't a bad work comms app if you're small enough not to need the compliance stuff. It gives you almost everything the big apps do for free, including unlimited calls, an advanced RBAC system, as many channels / messages as you want, a decent bot API (including media streaming), good notification management, multi-server / cross-organization support etc. They're actively disinterested in selling to businesses (which is what makes them so good, the features they paywall are the features needed by gamers, not serious professionals), but that also means you'll need to eventually migrate off of it when compliance requirements set in.
Earlier quoted context omitted.
We are being forced to dump slack for Teams. The only people who like Teams is Sales and Marketing for some reason. Not a single engineer likes this, and it will break every engineering convenience that exists on Slack.
As an ENG - I REALLY dislike teams - but I also dislike Slack Slack should be emails that have been arranged into different folders - it just doesn't vibe with me for much otherwise (oo look you have 200 channels on unread - or, if you are the reverse, ooo look 200 channels with people chatting and I have to check every single one of them :(
Earlier quoted context omitted.
As an ENG - I REALLY dislike teams - but I also dislike Slack Slack should be emails that have been arranged into different folders - it just doesn't vibe with me for much otherwise (oo look you have 200 channels on unread - or, if you are the reverse, ooo look 200 channels with people chatting and I have to check every single one of them :(
I hate unified inboxes with a burning passion.
> Microsoft did, and Teams is by all reports a solid success. Not sure if the author has used Teams. But otherwise, I agree we need an actual good, adorable Slack clone. I thought Google might do this after not buying Slack, but I'm not hearing anything about their solution.
Teams is shovelware. Force bundled, with questionably reliable messaging, okay video calling (if your organization policies don't break it), and a fairly useless Phone System component that misbehaves often. Great for organizations that believe these forms of communication should be an afterthought that has rough edges and inconsistent reliability. The recent changes to end webhook support, kill Linux desktop support…
I'm more interested in the fact that disclaimer at the top makes me think the entire article is written by AI as a summary of a bunch of reddit posts and tweets and discord topics? Is that what the top says?
Most of the article was written by AI I guess, but I think there's some human editing to it and the OP is the editor
> Microsoft did, and Teams is by all reports a solid success. Not sure if the author has used Teams. But otherwise, I agree we need an actual good, adorable Slack clone. I thought Google might do this after not buying Slack, but I'm not hearing anything about their solution.
Teams is definitely a solid success. It is by no means a good app. Those two things aren't the same. Slack started with an aggressive "bottom up" approach, they made something actually good and got to worrying about the sales part later. You don't need sales as much when companies come to you, begging you for an actual contract that fulfills their enterprise requirements, knowing that rooting you out is almost imposs…
Earlier quoted context omitted.
My org went all in on Teams over 6 years ago. Removed all PBX systems and desk phones. Pulled out Cisco phones from 20 offices. Ported all numbers to MS. By all accounts it was unremarkable to the end users, and when WFH mandates started it was seamless. Definitely a lot less IT support for configuring and troubleshooting a phone system too. There is far less downtime because Teams will ring through to your cell phon…
> That was not possible when the Cisco routers and CallManager in the office were running the DIDs and local extensions You could do it with other software hosted outside the office though. There are definitely options here.
Earlier quoted context omitted.
My org went all in on Teams over 6 years ago. Removed all PBX systems and desk phones. Pulled out Cisco phones from 20 offices. Ported all numbers to MS. By all accounts it was unremarkable to the end users, and when WFH mandates started it was seamless. Definitely a lot less IT support for configuring and troubleshooting a phone system too. There is far less downtime because Teams will ring through to your cell phon…
[flagged]