Live data from Hacker News

MS Teams channels cannot contain MS-DOS device names

learn.microsoft.com

21–30 of 364 posts

Re: MS Teams channels cannot contain MS-DOS device names

#24
Why is it that most "chat/conference" apps become horrible sooner or later? I still remember when teams used to be an OK app. It even had a Linux desktop client. I remember when slack was actually fast, I remember Skype out being more reliable to make phone calls than my mobile/cell service. Today slack is extremely slow if you add few organisations to it (but at least you can add more than one). Teams has deprecated their Linux desktop client and the only way to use it on Linux is via chrome, but wait, if you use it as part of office365/sharepoint you need to use Firefox for "some" sharepoint links. So essentially you need 2 browsers at all times. Chrome for teams (screen sharing and video), Firefox for some sharepoint links.

Re: MS Teams channels cannot contain MS-DOS device names

#26
post #22

This is such a Microsoft thing to do. DOS compatibility will haunt us for the rest of this century at least.

Sometimes I wish we had fresh clean slate OS.

Not the baggage of DOS or Unix... Something modern and sensible without insanity of either system.

Re: MS Teams channels cannot contain MS-DOS device names

#30

Ahahaha, I love this! I love how this new fandango thing harkens back to the earliest days of MS-DOS when it ran on a 086 or 286, back in the early (very early) 90s. Have to respect MS' backwards compatibility fanaticism. Impossibly as if a native port of MS Teams would be created for MS-DOS 3.1 (hahahaha). When more plausibly the MS Teams servers run on an ancient crazy proprietary MS-DOS 3.1 mainframe (still implau…

earliest days of MS-DOS when it ran on a 086 or 286, back in the early (very early) 90s.

About a decade off: MS-DOS was running on 8086 in the early 80s.

Post reply on HN