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: Cryx <email@hidden>
- Date: Wed, 3 Jul 2002 19:51:42 -0500
On Wednesday, July 3, 2002, at 09:38 AM, Kirk Kerekes wrote:
On Tuesday, July 2, 2002, at 10:57 PM, cocoa-dev-
email@hidden wrote:
You are also assuming that OS X systems don't have to unknowingly
interact with foreign and remote filesystems.
Sure they do -- just like they have been doing all along. The MacOS
didn't start with Cocoa, you know -- it has been around longer than
'step. There is a whole set of nice, mature, well-documented tools for
safely handling multi-forked files in a single-fork environment.
Cocoa's crime is that it has totally ignored the issue -- it doesn't
even acknowledge that forked files exist. This is a major shortcoming
on Cocoa's part, and it needs to be _fixed_ instead of denied.
You seem to infer that I'm an alien invader of the Mac world, yet I've
been a loyal Apple fan since the II+ days. Apple created an island for
itself and judging from "our" market share, the world has passed "us"
by. To play catch up, Apple has to make some tough decisions.
Macs, largely due to resource forks, have been terrible network
citizens. To claim otherwise is naive. I'm relucantly glad that Cocoa
is ditching forks. I look forward to the day of everyone using
something akin to xml wrappered file formats.
There are industry-wide standards for dealing with forked files
(AppleSingle/AppleDouble), and these standards include "magic cookie"
values for identification by alien filesystems. Every competent
webserver package supports and recognizes applesingle/appledouble.
You don't understand the concept of being a good network citizen. It's
got nothing to do with web servers and email attachments playing games
with file encodings. It's got everything to do with being able to mount
and export filesystems to or from any other system.
The Mac can no longer afford to be an island to itself, in the sense
that it can only transparently interact with same-system peers via
proprietary protocols. Try supporting Macs in a heterogeneous
environment of Windows and various Unices. For central file servers,
forks and encodings cause nothing but problems and grief.
It is time for Cocoa to 'get with the program'.
Apple is making tough decisions in order to secure future growth. The
market has already spoken by throwing Macs off the office networks. I,
for one, can only dream of the day when I'll be allowed to use a Mac at
work again (the company that makes our G4s). OS X has possibly brought
that day closer. Now if only Rational would port Clearcase...
Apple and Cocoa ARE with the program. For Apple's sake, you should be
too.
Daryn
_______________________________________________
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.