Comment by sigmoid10

> I don't need one app to do everything half-assed

That's primarily why it sucks, and that seems to be Microsoft's standard operating procedure. Everything they put out is in the category of "does everything, but half-assed with a web of fragile "integrations" that break if you look at it funny."

Worse, it's all SharePoint all the way down. Every team (and private channel!) is a SharePoint site, every user's OneDrive in the same tenant is a personal SharePoint Site. Every M365 Group gets its own SharePoint site (and mailbox). Creating a Team also creates an M365 group, but not vice versa.

Heaven forbid you rename something in the stack or you are in for a world of pain.

It's also by design that way. SharePoint storage is expensive, and boy what a disaster it is to ever try and get your data out of it.

Yet, for some reason, companies keep buying it and keep using it, letting Microsoft suck them in and hold them there for eternity.

If you're starting a new company, never, ever, buy anything Microsoft. Just don't go down that road. It's not worth it.

It’s not why your big corp chooses teams and the msft suite. From a corp perspective they don’t care about your edge case. There’s only - is it good for 90% of my use cases across the enterprise? And - do I get a bundle discount? Last but not the least - do I need to expend developer resources on it vs anything else?

Yeah, there is half assed stuff. But it’s not what most of the big corp uses anyway. So your little dev specific use case isn’t going to get much traction.

Teams does one thing well. It can do group chats and team calls. That’s most of what people use it for. And your corp gets a discount bundle.

If you don’t want a half assed simulacra version, shouldn’t you prefer Teams open the native application?