3 ms·
They only took uh... 6 years to finally let you move the annoying bar when you're screen sharing, which always gets in the damn way of either a browser tab you
by giancarlostoro 1y ago
They only took uh... 6 years to finally let you move the annoying bar when you're screen sharing, which always gets in the damn way of either a browser tab you need, or hitting Debug in Visual Studio. Drove me to hatred of Teams.
I also really hate that "Teams" within Teams don't have normal text channels like Slack or Discord, they're forums. I can't stand this design choice and refuse to use it.
It's such a frustrating app where the bar to entry was insanely low. I do like their office integration, but its like, well you couldn't have butchered that up.
- ffsm8 1y agoIf you click on that bar and press ctr-w it goes away without stopping the sharing. That was a mind blown for me when someone told me about that... Not sure how anyone found out about it, I man wouldn't anyone expect that to... Stop sharing too?
- ngrilly 1y agoI've never seen a "normal" user not confused by the difference between Teams's teams and Teams's channels (where every "channel" belongs to a "team"). I'm pretty sure that's reason #1 why most users use only group chats and never use channels. They simply don't understand how it works because it's too confusing.
- rectang 1y ago> Teams don't have normal text channels like Slack or Discord, they're forums If you can get notifications sorted out and allow notification on creation of a topic but not on messages within a topic, I really like this choice. The plague of Slack is constant pings in a channel that you need to need to monitor and thus can't mute, thanks to participants who refuse to start a thread and insist on having extended conversations in the root of the channel. Forcing thread/topic creation solves that problem.