3 ms·
Can someone explain to me why Microsoft file and directory names are always so hideous? Like, what in the world is cd12, cd2, cd3, cd9? Somehow it gets worse w
by warent 4y ago
Can someone explain to me why Microsoft file and directory names are always so hideous?
Like, what in the world is cd12, cd2, cd3, cd9? Somehow it gets worse when you click into them.
- shanselman 4y agoThat’s not related to Microsoft the company. That’s a result of the archivist systems that I had to mess with to get this stuff restored from tapes and CDs. I didn’t feel like changing it too much. So blame me.
- yuchi 4y agoThanks for your effort. Having a piece of my childhood made open source makes me so happy.
- pseudosavant 4y agoConsider yourself blamed Scott! jk
- warent 4y agoMy comment definitely came across as rude and I apologize. Thanks for your work and for taking the time to provide a thoughtful answer :) I'd probably also have left it just as you did.
- shanselman 4y ago:)
- jml7c5 4y agoI prefer it this way! It's better to share the "rawest" backups and fix them up after they've been dumped into version control so that a history of changes is available.
- zamadatix 4y agoBeing near 30 years old a lot of the naming looks hideous because it was developed with 8.3 filenames. https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/18e63b13-ba43-4f5f-a5b7-11e871b71f14 https://docs.microsoft.com/en-us/openspecs/windows_protocols...
- mhh__ 4y agoThe migration away from having numbers in identifiers is a subtle but extremely important aspect of modern code quality I feel. Having worked on code thats at least 20 years older than me, by the far the hardest parts to work out are the func1, func2, func3.