Unfortunately
Unfortunately
Unfortunately
You're viewing a single thread.
What's so bad about it?
Teams pretends it's an app that can do a lot of things at once but for literally all of the things it pretends to be good at it is the worst possible choice.
At my office, it works flawlessly for what we use it for, which is video conferences and chat. We don't mess with the workspaces and stuff.
The only thing I truly hate about it is that you can't export a log of a chat. As a government worker, I'm waiting for the lawsuit over Open Records over the lack of that feature.
and let me not start with the android client or the non existing support for linux users
I've never run across any of that. There must be some implementation issue that affects some companies and not others, because the 2 places I've worked since Teams took over everything have been flawless on all of that (except for Linux- and I really don't care about that from a business perspective where everyone is going to use Windows).
Is your company the one with the golden fax machine that always flawlessly sends an recieves?
No seriously. We are a tech heavy company. The only not tech savvy persons are law and HR (in numbers: two people). Same for most of our customers. And I hear this shit break left and right several times a day. I wonder what your company does right that nearly every other one does wrong. Probably restricting this bloatware enough to make it work.
Such as?
I use teams all the time at work and it seems to do what it needs to do well. Calls/meetings work wel, chatting works well. It's not perfect, but more than good enough.
Sounds like it's working great for you- I wish it would for me too! I'm not OP but some of my main gripes are:
On top of that, I don't find teams makes me more productive, if feels like a constant distraction that modern corporate culture requires me to have, even though its a net drop in productivity. This last point is more on instant messengers as a whole, but it doesn't place me in a very charitable or forgiving mindset for interpretting Team' multitude of flaws.
In the time that I was forced to use it, an entire team of Microsoft engineers could not get a Linux version working. It's a bloody website wrapped in a browser and they could not get it to work. A single dude made a linux package that just worked until Microshits messed that up right on time for their "official linux release", which (surprise surprise) still refused to work completely.
Linux users kept having trouble sharing screens, sharing files, couldn't add backgrounds to video calls, and a bunch of other stuff. For a while I thought it was just Linux users, but Mac users were also having trouble (this was before the M1s came along). Mac users had cameras that failed, sometimes couldn't see anybody else's video (just black), were inaudible and had to reconnect, and more issues.
I have friends who have to use office 265 and the amount of issues they run into is just phenomenal. Passwords have to be changed semi-frequently (every quarter or something) and sometimes they don't sync across the entire system. OneDrive has issues with symlinks (or whatever windows calls them) - either it's a Microshit problem or a user problem, I can't tell, but moving a symlink can sometimes move all the data too.
Not all the products seem to be properly connected like events created in calendars might not create team links despite configured to do so and only add a team link to the meeting when created within the desktop app (a bug known for a few years now). There have also been problems with OneDrive and SharePoint with access rights not being the same, some files missing (hidden or straight up not synced), and a bunch of other things.
I've had friends on "workation" walk into my room asking if I could help them with "this microsoft issue" and tell them to straight up ask their support, because I left that turdball of an ecosystem long ago.Boy am I glad I did.