Re: Mac OS X 10.1 File Name Extension Guidelines
Re: Mac OS X 10.1 File Name Extension Guidelines
- Subject: Re: Mac OS X 10.1 File Name Extension Guidelines
- From: Karl Goiser <email@hidden>
- Date: Mon, 10 Sep 2001 10:43:58 +1000
At 2:29 PM -0500 9/9/01, Jonathan Hendry wrote:
...
Besides, the type is, undeniably, useful information. I find it reasonable
to put it where it's readily available.
...
Truthfully, unless someone stands up and fights against it - we'll have
computers 30 years from now that are 100,000 times faster but still require
us to use .txt to indicate the file is a text document.
Well, frankly, that's not a bad thing, because the information is
mostly there for _human_ consumption, because it _is useful information_.
But I can use _exactly_ the same arguments to support embedding
creation date, last modified date, or even file size in the file name!
Come on you guys! I bet that at least some of you have computer
science degrees (this is a programming forum, after all). Didn't you
study normalised forms? First normal form (1NF): "Each attribute
represents an atomic value (nondecomposible attributes)." [Object
Oriented Design, Grady Booch, 1991, p372].
And this is quite apart from the absurd _human_ issues of embedding
application lookup data in a user readable field. For example, if I
change a file from abc.jpg to abc.txt, what will happen? How do I
even know what application will attempt (and fail) to open this file?
If OS X willfully refuses to play well with other systems, it
won't be invited to play.
Since when was schoolyard peer pressure ever an argument for anything
beyond the length of your shorts?
Karl
--
----
Klaatu barada nikto