• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: ObjC API != Cocoa (Re: Another controversial question)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ObjC API != Cocoa (Re: Another controversial question)


  • Subject: Re: ObjC API != Cocoa (Re: Another controversial question)
  • From: "Erik M. Buck" <email@hidden>
  • Date: Wed, 5 Sep 2001 11:54:02 -0500

We have one thread saying that CREATOR codes MUST be used and resource forks
MUST be used because people will not settle for the lowest common
denominator required for ubiquity.

We have this thread that says ONLY the lowest common denominator, procedural
C APIs, will be acceptable because we can not anticipate everyone's
requirements.

I find it ironic that people want to ruin file interchange and rebel from
the lowest common denominator in one thread and demand the lowest common
denominator and deny the advantages of the "better" way in another thread.

Rhapsody is DEAD, and we are all poorer as a result.


  • Follow-Ups:
    • Re: ObjC API != Cocoa (Re: Another controversial question)
      • From: Finlay Dobbie <email@hidden>
References: 
 >Re: ObjC API != Cocoa (Re: Another controversial question) (From: Ken Tabb <email@hidden>)

  • Prev by Date: Re: prob a silly question
  • Next by Date: Re: ObjC API != Cocoa (Re: Another controversial question)
  • Previous by thread: Re: ObjC API != Cocoa (Re: Another controversial question)
  • Next by thread: Re: ObjC API != Cocoa (Re: Another controversial question)
  • Index(es):
    • Date
    • Thread