• 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: EOF Advocacy, Open Source?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOF Advocacy, Open Source?


  • Subject: Re: EOF Advocacy, Open Source?
  • From: Andre John Mas <email@hidden>
  • Date: Tue, 14 Aug 2001 18:33:24 -0400

On Tuesday, August 14, 2001, at 06:13 PM, Nat! wrote:

On Tuesday, August 14, 2001, at 10:07 PM, Eric Peyton wrote:
There are dozens of reasons why certain API's are not public. Supporting an API "forever" is a difficult and thankless task.

Good that you put the "forever" in quotes, coz the Apple "forever" really translates to "as long as convenient (for Apple)".

That is true, though they have to draw the line on backwards compatibility
at some point. What would be nice is if Apple could use the Java
deprecation approach, ie the API is still there, but they will give
about 3 years notice that things are going to go away.

IMHO, the truth is Apple has done a very good job on managing
backwards compatibility, while moving forward. Examples
include 680x0->PPC transition and the classic environment
for MacOS X. At the same time the move has been tougher for
those people who came from OpenStep.

I could go on, but I will stop here.

Andre

--
mailto:email@hidden


References: 
 >Re: EOF Advocacy, Open Source? (From: Nat! <email@hidden>)

  • Prev by Date: Re: References, etc. for learning Cocoa?
  • Next by Date: [Slightly OFF] Dedicated Server Anyone?
  • Previous by thread: Re: EOF Advocacy, Open Source?
  • Next by thread: Re: EOF Advocacy, Open Source?
  • Index(es):
    • Date
    • Thread