Re: Cocoa stripping resource forks: does Jaguar fix?
Re: Cocoa stripping resource forks: does Jaguar fix?
- Subject: Re: Cocoa stripping resource forks: does Jaguar fix?
- From: Kirk Kerekes <email@hidden>
- Date: Tue, 2 Jul 2002 15:00:44 -0500
On Tuesday, July 2, 2002, at 02:36 PM, email@hidden
wrote:
From: Ondra Cada <email@hidden>
On Tuesday, July 2, 2002, at 04:42 , Kirk Kerekes wrote:
Regardless, this doesn't alter the core point -- that Cocoa _silently_
strips significant portions of user files, discarding data with no notice.
Not quite. From Cocoa (or BSD, posix, shellscript, you-name-it, actually
anything but the one proprietary Carbon niche!!!) point of view of course
the exact opposite is true: some applications dare to put their data into
files by a quite strange, non-standard, and haphazard way (of storing
those data into another file, which uses the original filename as it was
a
folder -- terrible and quite non-standard idea!). Therefore, it is
*utterly natural* that such data are lost.
I knew that someone would leap in to defend the indefensible.
We are not working on a BSD system here, even though one is buried
underneath. We are working on a HFS+ filesystem that explicitly supports
resource forks.
And that pretty much ends the discussion. When working inside this
filesystem, it is reasonably to be expected that everyone plays by the
rules of the filesystem, and doesn't just haphazardly throw user data away
without notice.
Cocoa violates this expectation, and is thus FAULTY in this context, and
needs to be FIXED.
And of course it can be -- the Carbon core has plenty of techniques
available for upgrading Cocoa's rather limited and parochial understanding
of what a file is.
AppleSingle and AppleDouble are netwide standards for "de-forking" files
with a resource fork, and if Apple were to combine them with file packages
in a transparent, clever way, the whole problem could go away.
I suspect that Avie's buds at Apple are trying to force the nasty old
resource forks out of existence by _deliberately_ remaining incompatible
with them -- and they are happy to let us _developers_ take the heat when
users lose stuff. This is also reprehensible.
Resource forks will wither away anyway -- as fast as Carbon-based apps get
replaced by Cocoa-based ones. Forcing the issue by making Cocoa a bad-actor
in the filesystem is poor policy.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.