▲ 411 ▼ First Impressions (lemmy.ca) submitted 1 year ago by TheWaterGod@lemmy.ca to c/techsupportmemes@lemmy.ca 23 comments fedilink hide all child comments
[–] Onomatopoeia@lemmy.cafe 24 points 1 year ago (8 children) Don't blame the dev, it's all management's fault. permalink fedilink source hideshow 8 child comments replies: [–] givesomefucks@lemmy.world 27 points 1 year ago (7 children) Nah, Teams is total shit. I forget what it replaced, but it was basically AIM. 90s as hell, nothing ever happened unless you explicitly made it, and virtually never any connection issues. Teams insisting on being tied to Outlook and then "breaking" each other constantly is not worth the limited functionality. I can set a busy message on my own. permalink fedilink source parent hideshow 7 child comments replies: [–] nickhammes@lemmy.world 12 points 1 year ago (1 child) Legitimately, if AOL resurrected AIM as an internal messenger for companies, with no changes other than to make sure it runs on modern systems, it would be an improvement on Teams. permalink fedilink source parent hideshow 1 child comment replies: [–] shalafi@lemmy.world 2 points 1 year ago I ran an internal OpenFire VM for internal chat. Flawless. permalink fedilink source parent [–] Kyrgizion@lemmy.world 6 points 1 year ago (2 children) It replaced Skype (for business). permalink fedilink source parent hideshow 2 child comments replies: [–] themoonisacheese@sh.itjust.works 5 points 1 year ago At some point during Skype for business end of life, both teams and sfb were operating on the same protocol and that explains a lot of the weird design of teams permalink fedilink source parent [–] Zorque@lemmy.world 0 points 1 year ago Skype was terrible, though. permalink fedilink source parent [–] BCsven@lemmy.ca 4 points 1 year ago Skype permalink fedilink source parent [–] bus_factor@lemmy.world 3 points 1 year ago And I bet those design decisions were made by management, not the developers. Working on corporate tech as a developer means constantly making things you as a developer and/or user know is going to be shit, but the suits don't listen to reason. permalink fedilink source parent
[–] givesomefucks@lemmy.world 27 points 1 year ago (7 children) Nah, Teams is total shit. I forget what it replaced, but it was basically AIM. 90s as hell, nothing ever happened unless you explicitly made it, and virtually never any connection issues. Teams insisting on being tied to Outlook and then "breaking" each other constantly is not worth the limited functionality. I can set a busy message on my own. permalink fedilink source parent hideshow 7 child comments replies: [–] nickhammes@lemmy.world 12 points 1 year ago (1 child) Legitimately, if AOL resurrected AIM as an internal messenger for companies, with no changes other than to make sure it runs on modern systems, it would be an improvement on Teams. permalink fedilink source parent hideshow 1 child comment replies: [–] shalafi@lemmy.world 2 points 1 year ago I ran an internal OpenFire VM for internal chat. Flawless. permalink fedilink source parent [–] Kyrgizion@lemmy.world 6 points 1 year ago (2 children) It replaced Skype (for business). permalink fedilink source parent hideshow 2 child comments replies: [–] themoonisacheese@sh.itjust.works 5 points 1 year ago At some point during Skype for business end of life, both teams and sfb were operating on the same protocol and that explains a lot of the weird design of teams permalink fedilink source parent [–] Zorque@lemmy.world 0 points 1 year ago Skype was terrible, though. permalink fedilink source parent [–] BCsven@lemmy.ca 4 points 1 year ago Skype permalink fedilink source parent [–] bus_factor@lemmy.world 3 points 1 year ago And I bet those design decisions were made by management, not the developers. Working on corporate tech as a developer means constantly making things you as a developer and/or user know is going to be shit, but the suits don't listen to reason. permalink fedilink source parent
[–] nickhammes@lemmy.world 12 points 1 year ago (1 child) Legitimately, if AOL resurrected AIM as an internal messenger for companies, with no changes other than to make sure it runs on modern systems, it would be an improvement on Teams. permalink fedilink source parent hideshow 1 child comment replies: [–] shalafi@lemmy.world 2 points 1 year ago I ran an internal OpenFire VM for internal chat. Flawless. permalink fedilink source parent
[–] shalafi@lemmy.world 2 points 1 year ago I ran an internal OpenFire VM for internal chat. Flawless. permalink fedilink source parent
[–] Kyrgizion@lemmy.world 6 points 1 year ago (2 children) It replaced Skype (for business). permalink fedilink source parent hideshow 2 child comments replies: [–] themoonisacheese@sh.itjust.works 5 points 1 year ago At some point during Skype for business end of life, both teams and sfb were operating on the same protocol and that explains a lot of the weird design of teams permalink fedilink source parent [–] Zorque@lemmy.world 0 points 1 year ago Skype was terrible, though. permalink fedilink source parent
[–] themoonisacheese@sh.itjust.works 5 points 1 year ago At some point during Skype for business end of life, both teams and sfb were operating on the same protocol and that explains a lot of the weird design of teams permalink fedilink source parent
[–] Zorque@lemmy.world 0 points 1 year ago Skype was terrible, though. permalink fedilink source parent
[–] bus_factor@lemmy.world 3 points 1 year ago And I bet those design decisions were made by management, not the developers. Working on corporate tech as a developer means constantly making things you as a developer and/or user know is going to be shit, but the suits don't listen to reason. permalink fedilink source parent