----------------------------------------------------------------------------------
@MSGID: 1@dont-email.me> b7038f49
@REPLY: <dog_cow-1691758563@macgui.com> 7ab1a47f
@REPLYADDR David Schmidt <schmidtd@my-deja.com>
@REPLYTO 2:5075/128 David Schmidt
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 1@dont-email.me>
@RFC-References:
<d17b6039-834f-48e1-a497-e999884e895cn@googlegroups.com> <dog_cow-1691758563@macgui.com>
@TZUTC: -0400
@PID: Mozilla Thunderbird
@TID: FIDOGATE-5.12-ge4e8b94
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.
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.
--- Mozilla Thunderbird
* Origin: A noiseless patient Spider (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