MS Teams channels cannot contain MS-DOS device names

Re:MS Teams channels cannot contain MS-DOS device names by m00dy on Thursday August 10, 2023 @11:55AM (#37077812)

I can't be the only one thinking that generally MS Team is offering probably worst experience in the messaging market.

[ Parent | on HN ]

Re:MS Teams channels cannot contain MS-DOS device names by uraji on Thursday August 10, 2023 @12:21PM (#37078170)

you are not

[ Parent | on HN ]

Re:MS Teams channels cannot contain MS-DOS device names by rqtwteye on Thursday August 10, 2023 @12:50PM (#37078562)

Slack is working hard on catching up but Teams is definitely the leader in suckiness right now.

[ Parent | on HN ]

Re:MS Teams channels cannot contain MS-DOS device names by ilyt on Thursday August 10, 2023 @01:16PM (#37078890)

It's absolute fucking garbage when it comes to text chat. It boggles my mind that they had so many examples on how to do it right and fucked it up so badly

[ Parent | on HN ]

Re:MS Teams channels cannot contain MS-DOS device names by CSMastermind on Thursday August 10, 2023 @06:05PM (#37082378)

I honestly think they should fire every single PM on that team. Like literally just keep the engineers and give them no more direction than make it better and designers need to approve any UI changes.

That's it.

[ Parent | on HN ]

Re:MS Teams channels cannot contain MS-DOS device names by m00dy on Friday August 11, 2023 @03:19AM (#37086012)

I just called Satya and told him that he should talk to Pavel to get some advise for the UI experience.

[ Parent | on HN ]

Re:MS Teams channels cannot contain MS-DOS device names by Lio on Friday August 11, 2023 @07:04AM (#37087288)

I'm right with you on that.

Highlight some text, right click and select copy. Teams copies some other random text and not what you highlighted. Grrr!

Any product that can't even get basic copy and paste right is garbage in my opinion.

The only reason people use it is that it's bundled for "free" with MS Office.

[ Parent | on HN ]