Please let MS teams die
-
I'm talking to you corporate IT folks. Teams is an abortion. A world ending event. There are so many chat clients (and let's be honest, that's what MS wanted teams to be) out there that just elephanting work. I can't post a clip, but I've run into so many "We're sorry -- we've run into an issue." NO clue who we is. And after 30 elaphanting years, the solution is to restart or to sign out and log back in. In other words, REBOOT. If you work in IT, please save us. I'm going to go talk to customers in slack. Their team has a clue.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
I'm talking to you corporate IT folks. Teams is an abortion. A world ending event. There are so many chat clients (and let's be honest, that's what MS wanted teams to be) out there that just elephanting work. I can't post a clip, but I've run into so many "We're sorry -- we've run into an issue." NO clue who we is. And after 30 elaphanting years, the solution is to restart or to sign out and log back in. In other words, REBOOT. If you work in IT, please save us. I'm going to go talk to customers in slack. Their team has a clue.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
I'm with you.
-
I'm talking to you corporate IT folks. Teams is an abortion. A world ending event. There are so many chat clients (and let's be honest, that's what MS wanted teams to be) out there that just elephanting work. I can't post a clip, but I've run into so many "We're sorry -- we've run into an issue." NO clue who we is. And after 30 elaphanting years, the solution is to restart or to sign out and log back in. In other words, REBOOT. If you work in IT, please save us. I'm going to go talk to customers in slack. Their team has a clue.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
I use Slack for 'chat'. Teams for 'meetings'. Not sure I have ever posted a video to either. I think I have seen links to videos in Slack. Not sure if I care to post either. Videos tend to be larger binaries. I would expect both to have an absolute size limit on binaries which with videos in the stream one could probably run into then they would need to find a different file sharing method anyways.
-
I'm talking to you corporate IT folks. Teams is an abortion. A world ending event. There are so many chat clients (and let's be honest, that's what MS wanted teams to be) out there that just elephanting work. I can't post a clip, but I've run into so many "We're sorry -- we've run into an issue." NO clue who we is. And after 30 elaphanting years, the solution is to restart or to sign out and log back in. In other words, REBOOT. If you work in IT, please save us. I'm going to go talk to customers in slack. Their team has a clue.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
I don't have any issues with MS Teams. I use it all day long. Our entire company uses it all day long - chat, video, apps, everything. Instead of blaming Teams, you might want to start blaming the IT department (if you have one) that manages Teams.
-
I'm talking to you corporate IT folks. Teams is an abortion. A world ending event. There are so many chat clients (and let's be honest, that's what MS wanted teams to be) out there that just elephanting work. I can't post a clip, but I've run into so many "We're sorry -- we've run into an issue." NO clue who we is. And after 30 elaphanting years, the solution is to restart or to sign out and log back in. In other words, REBOOT. If you work in IT, please save us. I'm going to go talk to customers in slack. Their team has a clue.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
charlieg wrote:
And after 30 elaphanting years, the solution is to restart or to sign out and log back in. In other words, REBOOT.
MS can't stand it when another company has a good product and dominates a market. The problem with that is, you can only spread your sights so far before your main products suffer - even with the money of MS. Microsoft's claim to fame was Windows and Office, and let's be honest here... BeOS floored both MacOS and Windows. Windows had _some_ cool improvements, but not much. Come to think of it, MS should've bought that out before Palm crushed it. But no, we get Teams. :laugh:
Jeremy Falcon
-
I don't have any issues with MS Teams. I use it all day long. Our entire company uses it all day long - chat, video, apps, everything. Instead of blaming Teams, you might want to start blaming the IT department (if you have one) that manages Teams.
Slacker007 wrote:
Instead of blaming Teams, you might want to start blaming the IT department (if you have one) that manages Teams.
There might be some truth to this. Alls I know is though, I've had Teams crash my computer hardcore when sharing my screen for more than 40 minutes in meetings. It's happened more than once. I'd like to think even if IT made some terrible choices in setting it up that Teams would at least crash gracefully.
Jeremy Falcon
-
I use Slack for 'chat'. Teams for 'meetings'. Not sure I have ever posted a video to either. I think I have seen links to videos in Slack. Not sure if I care to post either. Videos tend to be larger binaries. I would expect both to have an absolute size limit on binaries which with videos in the stream one could probably run into then they would need to find a different file sharing method anyways.
-
I don't have any issues with MS Teams. I use it all day long. Our entire company uses it all day long - chat, video, apps, everything. Instead of blaming Teams, you might want to start blaming the IT department (if you have one) that manages Teams.
-
I'm talking to you corporate IT folks. Teams is an abortion. A world ending event. There are so many chat clients (and let's be honest, that's what MS wanted teams to be) out there that just elephanting work. I can't post a clip, but I've run into so many "We're sorry -- we've run into an issue." NO clue who we is. And after 30 elaphanting years, the solution is to restart or to sign out and log back in. In other words, REBOOT. If you work in IT, please save us. I'm going to go talk to customers in slack. Their team has a clue.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
We use Teams, company wise, for chat and meetings and all... No problem I can complain... I even developed a packsge of plugins that our customers use to turn Teams into a learning platform for online courses...
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." ― Gerald Weinberg
-
We use Teams, company wise, for chat and meetings and all... No problem I can complain... I even developed a packsge of plugins that our customers use to turn Teams into a learning platform for online courses...
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." ― Gerald Weinberg
Kornfeld Eliyahu Peter wrote:
I even developed a packsge of plugins that our customers use to turn Teams into a learning platform for online courses...
that would be a good content for an article ;)
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
I'm talking to you corporate IT folks. Teams is an abortion. A world ending event. There are so many chat clients (and let's be honest, that's what MS wanted teams to be) out there that just elephanting work. I can't post a clip, but I've run into so many "We're sorry -- we've run into an issue." NO clue who we is. And after 30 elaphanting years, the solution is to restart or to sign out and log back in. In other words, REBOOT. If you work in IT, please save us. I'm going to go talk to customers in slack. Their team has a clue.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Many companies I worked for tried to get away from Lync/Skype/Teams. Every single one of them failed: there will always be at least one customer or provider who adamantly refuses to use anything else, so you're forced to keep it and use it every time some of those customers / providers needs to be in call, which means that it becomes the standard.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X The shortest horror story: On Error Resume Next
