[lpbonenfant]

I don't understand most of the negative comments in this thread along the lines of "if my company would require I use Teams I'd quite on the spot". Really? an IM client is what's going to make you quit? I always thought it was amusing that old developers were super anal about vim vs emacs and saw it as a tongue in cheek but now I realize most of those people are really serious and take these things quite emotionally...

[jdlshore]

It's a tool that people use day-in, day-out for all their communication with colleagues. If it's unpleasant to use, the majority of your work becomes a constant reminder of that unpleasantness.

[gabrielgio]

Exactly, if my chat, my email, my git server, etc. are unpleasant it will make my workflow unpleasant and so will my job as whole. I have changed jobs due tooling being a pain before.

I'd never quit on the spot though, I'd silently search for another job.

[brulard]

It's a collaboration tool, not just some IM client. After 6 years of using Slack I have to use Teams now on a project I lead. Oh boy, it's so much worse. I completely agree that it can make you leave, especially when you are responsible for efficient collaboration and tool like this is constantly in the way. It discourages communication between teammates, channels and threads are a mess so everyone rather DM people directly (so transparency suffers a lot). Everyone regardless of the OS have problems getting notifications, the threads are a joke, so are the reactions. It's so hard to find anything there, channels (teams?), a message, a user. I haven't seen an integrations/bots/apps in teams, maybe they are there, but in Slack they were so useful and easy to add, that they were used so much.