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.
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.
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
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.
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.
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.
IRC.
Fuck yes. If my company would allow it, I’d insist my team communicate on an internal IRC server.
I ran an internal OpenFire VM for internal chat. Flawless.
It replaced Skype (for business).
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
Skype was terrible, though.
Skype
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.