zlacker

>>AareyB+(OP)
Refreshing. No more Teams? Sounds like a dream... Of all the crapware I am forced to work with, Teams really pushes the envelope in every single negative way conceivable. I think I have more love for SharePoint than Teams, and that is a massive concession.

>>pelagi+2c
It's not that bad. It's well integrated into Sharepoint, Exchange, and Office, and does the job. I've used both Slack and Teams and if you're using MS365, then Teams is absolutely the better option.

>>macspo+zi
As someone who has gone from 100% Slack in startups to all-in Teams in big corpo, I disagree. Teams won't even display all office file formats without you having to open the dedicated app. And if it does it's usually a half-baked browser mess. And don't even get me started on the UX or meeting options or mobile support or the complete lack of a dedicated Linux client. I don't need one app to do everything half-assed, I need one app that does exactly what it's meant for well. Preferably on every platform.

>>sigmoi+Ql
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.