• 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 - was (Cocoa Books (was New to Cocoa) )
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOF - was (Cocoa Books (was New to Cocoa) )


  • Subject: Re: EOF - was (Cocoa Books (was New to Cocoa) )
  • From: Sherm Pendley <email@hidden>
  • Date: Tue, 15 Oct 2002 11:54:47 -0400

On Tuesday, October 15, 2002, at 10:16 AM, David W. Halliday wrote:

William Moss wrote:

Maybe it was for technical reasons. ...

The fact that they are still doing it in a (slightly) technically inferior
language (Java) suggests this is not the case.

The fact that they're doing it in Java suggests, to me, that they want to leverage existing JDBC adapters, instead of trying to convince 3rd party database vendors to develop a native EOF adapter.

There is a technical aspect to it, in that it would be difficult to make JDBC adapters available to an Objective-C code base. But, there are also political aspects relating to third party vendors, as well as financial - it costs real money to maintain the Objective-C version.

Instead of considering the current situation, try to consider Apple's situation a couple of years ago - they were trying to ship an OS that was already years late from the public's point of view, after a couple of previous aborted attempts. Vendors were rebelling against having to rewrite their Classic apps in Objective-C, while at the same time fawning over Java in the server app arena. I can't really find fault in their failure to anticipate the warm reception that ObjC would receive among Cocoa developers, nor the cold shoulder that Java would get.

Apple has been doing many things right recently, so it's sometimes easy to forget that the crystal ball in Cupertino is sometimes a bit cloudy. I'd like to see EOF for ObjC as much as anyone, but I can understand what drove Apple to drop it in the first place, even though looking back with the benefit of hindsight now shows that to be a bad idea. I simply hope that they're big enough to admit their mistakes and correct them.

(There are technically superior languages I would like Cocoa to evolve toward,

We already have Objective-C, Java, AppleScript, Perl, Python, and Ruby. What do you want, mermaids? :-)

sherm--
_______________________________________________
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.

  • Follow-Ups:
    • Perl & Cocoa
      • From: "Steven M.Palm" <email@hidden>
    • Re: EOF - was (Cocoa Books (was New to Cocoa) )
      • From: "David W. Halliday" <email@hidden>
References: 
 >Re: EOF - was (Cocoa Books (was New to Cocoa) ) (From: "David W. Halliday" <email@hidden>)

  • Prev by Date: Re: Keyboard shortcuts for views in toolbar items
  • Next by Date: Re: Keyboard shortcuts for views in toolbar items
  • Previous by thread: Re: EOF - was (Cocoa Books (was New to Cocoa) )
  • Next by thread: Re: EOF - was (Cocoa Books (was New to Cocoa) )
  • Index(es):
    • Date
    • Thread