----------------------------------------------------------------------------------
@MSGID: <dog_cow-1691962859@macgui.com> 5dcdd08e
@REPLY: 1@dont-email.me> b7038f49
@REPLYADDR D Finnigan <dog_cow@macgui.com>
@REPLYTO 2:5075/128 D Finnigan
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: <dog_cow-1691962859@macgui.com>
@RFC-References:
<d17b6039-834f-48e1-a497-e999884e895cn@googlegroups.com> 1@dont-email.me>
@TZUTC: -0000
@PID: Mac GUI Usenet
@TID: FIDOGATE-5.12-ge4e8b94
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/
--- Mac GUI Usenet
* Origin: Mac GUI (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441