Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.sys.apple2    |    Discussion about Apple II micros    |    56,720 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 56,274 of 56,720    |
|    D Finnigan to David Schmidt    |
|    Re: CP/M filesystem questions    |
|    13 Aug 23 21:41:01    |
      From: dog_cow@macgui.com              David Schmidt wrote:       > On 8/11/23 8:56 AM, D Finnigan wrote:       >> fadden wrote:       >>> The CP/M filesystem continues to delight and terrify me.       >>>       >>       >> If computer file systems had been designed by persons with secretarial       >> experience, perhaps they'd be less brain-damaged.       >>       >> Even now it's an arbitrary limitation against more than one file having       >> the       >> same file name in a directory, even when there are plenty of practical       >> use       >> cases for having multiple files with the same name in a directory with       >> differing modification or creation dates.       >       > Heh. What would happen is secretaries would have (root) directories       > full of files that all have the same name but differ /only/ by the date.              Sure why not? Let's say you have a directory of annual reports from 1980 to       1989. They ought to all have the same file name "Annual Report" and       differing dates for each year.                     >       > Or... my favorite. Do you know what HFS allows? TRAILING WHITESPACE.       > Do you know what's practically impossible to see? TRAILING WHITESPACE.       > Allowing arbitrary crap like spaces, backslashes, whitespace, or       > whatever else the secretary barfed on the keyboard is great only if       > there is a deterministic way to know a file by another (saner,       > automatable, deterministic) handle. Lots of dedicated word processing       > systems did exactly that... you have a file with a slug and a date, and       > you can barf all you want into the metadata section.       >              A lot of what he have today is self-inflicted damage from choice of       command-line user interface. The classic example being spaces in filenames       when using a CLI with argument switches. The user interface could have been       designed a lot differently.                            --       ]DF$       The New Apple II User's Guide:       https://macgui.com/newa2guide/              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca