71–80 of 364 posts
Teams is so weird, “ Number of org-wide teams allowed in a tenant” is limited to 25. So my company can only have 25 “general” teams. I think it would be neat to learn the rationale behind some of these settings.
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.
But 'forms'? Why is 'forms' a bad word?
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 a classic joke, but settling on a common gauge was really difficult, it was not just copying some old Roman standard. There were even riots when different railways started to standardize because common rail gauge meant you can move through the town without engaging with the local economy, see Erie gauge war. Russia still has a wider gauge than Europe and Australia has 3 different ones.
Likewise, in the Canadian House Of Parliament, the width between the Prime Minister's desk and that of the Leader Of The Opposition is said to be that of two swords raised, tip to tip, based on the British House Of Commons tradition that they must remain ''two swords and one inch apart.''
Earlier quoted context omitted.
most of those are the usual forbidden path and filename characters. % is used to surround environment variables for interpretation, for example.
> the usual forbidden path and filename characters. It’s pretty irritating when files and folders on my Mac can’t be uploaded to Teams due to this limitation. It’s only forbidden for Windows users.
I think the only character that Macs don't allow is the colon. AFAIK, everything else is fair game, even emojis.
I just created a project with "ê" in the title. I wonder if I'll be able to share that with my Windows coworkers on Teams.
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?
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.
Earlier quoted context omitted.
> the usual forbidden path and filename characters. It’s pretty irritating when files and folders on my Mac can’t be uploaded to Teams due to this limitation. It’s only forbidden for Windows users.
It’s only forbidden for Windows users. I think the only character that Macs don't allow is the colon. AFAIK, everything else is fair game, even emojis. I just created a project with "ê" in the title. I wonder if I'll be able to share that with my Windows coworkers on Teams.
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.
I worked on a sharepoint project once. Let's just say I'm not putting it on my resume these days.