On 12 Dec 2011 at 15:39, Richard wrote:
Good dog, no. The resource fork is horrible IMO.
Granted, it's not perfect. But it's better than no hint at all as to
what a file might represent. The DOS/whatever convention of filename-
extension-dictating-content-type is nearly useless as the number of
applications balloons. It's a free-for-all out there, so an
extension of XPZ, for example, can mean anything and gives no hint of
what might have created the file.
While there are web sites such as
http://www.fileextension.org/ that
offer suggestions, there are plenty of applications using similar
extensions that bear no relation to those applications itemized.
If this were a better world, each file would be preceded by an ID
block that identified the program creating the file; the name of the
last program to modify the file and other such useful information.
User applications would be locked out from modifying that
information, although they could freely interrogate it.
--Chuck