[nullymcnull]

No surprise at the MS non-response here. Anyone forced to use Teams every day can see that it's being maintained by a skeleton crew (at best) on the dev side. Every single day I miss basic features (like global message linkability) that I came to love in Slack, and suffer 101 little bugs and annoyances that never seem to improve much.

MS clearly thinks Teams is "good enough" - enough of the feature checkboxes ticked that they can focus mostly on aggressively marketing it, making it seem crazy to use a separate third-party chat platform instead of Teams if you're using Azure.. even if does happen to be a buggy bloated beast, with almost unusably wretched mobile apps.

If there's just one area I wish we hadn't switched to MS-brand dogfood after making the move to Azure, it's chat/calling. It's a deceptively tricky domain to get it right in, and one where you really want as little friction as possible for all users.

"We should have stuck with Slack." - every team that ever switched to MS Teams.

[hnthrowaway0315]

I think starting from maybe 5-6 years ago MS got into the mindset of "pushing early and let users be beta testers and do micro patches along the way". Power BI was CLEARLY only barely useable back in 2017 but gradually climbed out of the hole after 2019.

More and more I wish I could work in some company that doesn't use any MS tools. VSCode seems to be the exception here.