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.
There is a better software for that. Teamcenter PLM. Centralized database, each user can organize the data into their own "folders" if they like, but you find data by its meta data, and checkout and revisioning is controlled properly
For text communication, teams sucks. Channels and groups are weirdly different. Channel and normal meetings are weirdly different. search is f'ed up....
I work at... Linux?
Don't blame the dev, it's all management's fault.
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.
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.
And lose the chance to blackmail them into improving the program? Shortsighted.
Yeah I think castle doctrine gives you the right to kill him on the spot
Or Sharepoint.
It's so much harder to search for files in a company wide network drive without folder management.
There is a better software for that. Teamcenter PLM. Centralized database, each user can organize the data into their own "folders" if they like, but you find data by its meta data, and checkout and revisioning is controlled properly
That's letting a war criminal off easy. I'd string him up.
Hot take: Teams is fine. Better than Slack or Zoom.
For text communication, teams sucks. Channels and groups are weirdly different. Channel and normal meetings are weirdly different. search is f'ed up....
Zoom: yeah that's worse for text communication
Not much of a hot take
It isn't perfect but it is decent especially in the last few years
Yeah but Legal Sharks
as an estonian, he's dead