61–70 of 364 posts
Words: forms, CON, CONIN$, CONOUT$, PRN, AUX, NUL, COM1 to COM9, LPT1 to LPT9, desktop.ini, _vti_
Earlier quoted context omitted.
Yeah those 8+3 file names sure birthed some creative abbreviations. Necessity, mother, all that
Brevity forces thought, which I prefer to "Putting a Sentence in a File Name.docx". FORTRAN originally had the same limitation for function names, and that lead to some classics such as GEMM and SAXPY.
I was about to say "Which is essentially leaking the existence of something terrible inside. They should be embarrassed to say something like this in public. Like saying you can't have %s or $PS1. Why the hell not? What are you doing with this user-supplied input?" But maybe it's more about what everyone else might do with a channel name. Ie they might cut & paste it anywhere, and I guess windows users aren't expecte…
they're SharePoint limits, man. Teams is backed by SharePoint and it's not a secret, nor is it embarrassing.
Isn’t it? The folders work fine on a Mac.
Teams is not a things of beauty, and is rough as all hell for daily users.
Having to escape everything or replace names with stable guids is not a good relpacement for storing \whatever\logs\channelname or whatever the need may be. Especially for systems that are hard bound to windows filesystems or Sharepoint to begin with.
I bet there are apps on other OS:es where you CAN name things a "\0" sequence or "/" and for each such app I imagine there are people who regret making that possible.
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 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.
Earlier quoted context omitted.
Agree BC is a laundable goal and appreciate their efforts. Though I do wish it didn't include limiting passwords to obscenely short lengths or absurd subsets of characters.
Yeah those 8+3 file names sure birthed some creative abbreviations. Necessity, mother, all that
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?