zlacker

>>basemi+(OP)
The official client is absolutely terrible. But, I've found a much better solution: I tell all my customers Microsoft Teams doesn't work for us and they'll have to pick something else.

Kudos for at least trying to address this, MS should hang their head in shame, this is not the hardest problem to solve these days. If we could do it in 1995 they should be able to do it 30 years later.

>>jacque+G6x
From a UI perspective, Teams is terrible, but there is one thing it does well and that's large meeting calls. Microsoft knows their customers: large companies.

The boss doesn't see that you can't properly paste a piece of code in the chat, but he wants to make sure that everyone hears him at the annual talk. He wants it to connect to the company directory, make analytics, reflect the corporate hierarchy, make announcements, etc... He sees it as a one way, top down communication tool more than peer-to-peer, and for the former, Teams delivers. Developers hate it, but developers are not the ones who have the money and make these decisions.

Still, that's a thing I miss about Bill Gates's Microsoft. It was certainly evil (Embrace Extend Extinguish, the fight against free software, etc...), but at least, they actually cared about usability and developers, not just pleasing big company bosses.

>>GuB-42+TQx
> The boss doesn't see that you can't properly paste a piece of code in the chat

Of all my many gripes with Teams, it usually handles code surprisingly well. Single `inline` and triple backtick blocks usually render as you'd expect.

OneNote on the other hand doesn't support a code-block at all, and is worse (if you can believe it) than storing cli commands in Word docs.