Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MS Teams channels cannot contain MS-DOS device names

learn.microsoft.com

Post reply on HN
Print view View original

131–140 of 364 posts

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

#131

Post by Nzen »

mordae wrote: post #31
air7 wrote: post #21

This backwards compatibility chain reminds me of the age old tale of how rockets are the width of two horses... (1) (1) http://astrodigital.org/space/stshorse.html

This is pure gold. Thanks, you made my day! :-) Also, you might be interested in this: https://youtu.be/1NqRbBvujHY?t=2236

While I enjoyed rewatching the latter half of episode 2 of season 1 of James Burke's Connections tv series, I don't see how the invention of the cloud chamber (which you start the video at) is relevant to standards for rail, horses, or rockets. What's the connection ?

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

#132

Post by yjftsjthsd-h »

extraduder_ire wrote: post #123
yjftsjthsd-h wrote: post #106

Earlier quoted context omitted.

> AFAIK, everything else is fair game, even emojis FWIW, I generally expect emojis to be more compatible than other symbols, because they have no legacy meanings - ex. ™ has never been a path separator, or indeed anything else.

Main problem with "emojis" is that they live outside the basic multilingual plane, and so make bad utf-16 handling really obvious. This is a blessing in disguise, because it acts as a no-brown-m&ms thing, since it's more unarguably broken than not being able to use cuneiform, or musical symbols.

Yeah, point; I probably should have said something more like "emoji shouldn't have alternative meanings, so they should work if your unicode support is functional (which is a big caveat)." On the bright side, yeah, emoji have been great at pushing things to handle unicode nicely and act as a... I dunno, natural fuzzing case?

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

#133

Post by masklinn »

Svip wrote: post #60
air7 wrote: post #21

This backwards compatibility chain reminds me of the age old tale of how rockets are the width of two horses... (1) (1) http://astrodigital.org/space/stshorse.html

The Romans did not use war chariots, since they are basically useless in combat. They only used chariots for sports in the hippodrome.

Chariots are not “useless in combat”, but they are very expensive to field and only work in pretty narrow circumstances: wide, open, and relatively solid areas (aka not bogs).

These circumstances were not a thing for Roman legions until they reached spain at least, possibly North Africa and the Middle East. As a result they were not part of Roman war doctrines.

On the other hand they were very much part of bronze-age Egyptian and Hittite armies.

An other factor to their lack of appeal tho may have been improvements in horse riding technique and gear, as well as training. Riders can also be heavily armed, but have less travel restriction, and you can field a warrior per horse rather than need two horses and a driver per.

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

#135

Post by msla »

mordae wrote: post #31
air7 wrote: post #21

This backwards compatibility chain reminds me of the age old tale of how rockets are the width of two horses... (1) (1) http://astrodigital.org/space/stshorse.html

This is pure gold. Thanks, you made my day! :-) Also, you might be interested in this: https://youtu.be/1NqRbBvujHY?t=2236

It's a dumb joke with no basis in fact.

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

#136

Post by kevincox »

ant6n wrote: post #18
icegreentea2 wrote: post #12

Earlier quoted context omitted.

Not necessarily - it could mean that at some point they believe they'll need to create folder or file with the same name as a team, and they don't wanna have to deal with weird collisions. It's been a while since I've used Teams+Sharepoint, but I vaguely remember being able to have a Sharepoint workspace per team channel, and then being able to mount those workspaces as a shared/network drive. Stuff that might end up…

This%20is%20what%20escape%20sequences%20are%20for.

If these folders are user-visible (for example browsable in SharePoint) then this leads to a bad user experience. The downside of restricting channel names needs to be weighed against the downside of needing to escape the SharePoint folder names.

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

#137

Post by r0b1n »

Svip wrote: post #60
air7 wrote: post #21

This backwards compatibility chain reminds me of the age old tale of how rockets are the width of two horses... (1) (1) http://astrodigital.org/space/stshorse.html

The Romans did not use war chariots, since they are basically useless in combat. They only used chariots for sports in the hippodrome.

They used chariots not only in the hippodrome, also for processions and other "shows".

But Roman warfare was a no-nonsense kind of affair, so no chariots. https://acoup.blog describes this really well.

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

#139

Post by Anthony-G »

glonq wrote: post #70
keepamovin wrote: post #37

Earlier quoted context omitted.

Yeah those 8+3 file names sure birthed some creative abbreviations. Necessity, mother, all that

Whenever I create a filename that is long or has spaces, I still pause and worry "okay, what might break if I do this", even though such concerns probably died a couple decades ago. Actually scripts breaking if files or paths have a space in them seems to be a thorn in the side of dev/ops/it folks that never goes away, does it?

Unix shell scripts will break when filenames/paths have spaces if variable expansions are not quoted, resulting in word splitting and filename expansion (globbing). This is something that is drilled into learners by all good teachers, e.g., https://mywiki.wooledge.org/Quotes#When_Should_You_Quote.3F
Post reply on HN