On Jun 14, 2007, at 5:46 PM, Laurence Harris wrote:
On Jun 14, 2007, at 7:58 PM, Steve Christensen wrote:
What everyone seems to forget is the Carbon was always described
as a method for a relatively smooth transition of OS 9's "legacy"
procedural APIs onto OS X so that developers could get their
products running sooner, not as something that would be around
forever.
That hasn't always been the official description. If that were the
case then why have an announcement at last year's WWDC that Carbon
would get 64-bit support? Why introduce an all new interface model
(HIView) in the third major release of Mac OS X? Why would people
want to abuse themselves carbonizing an old application just to
have to redo it all again later in Cocoa?
Well, the easiest answer might have been that Apple engineers weren't
focusing initial effort on a move to 64-bit Carbon, focusing on other
features, Cocoa, etc. Then when they seriously delved into it, they
realized that there were some major issues that couldn't be solved.
Or perhaps management decided that 32/64-bit would be a good cut-off
point and that those engineering resources could be better used
elsewhere.
I wasn't in on any of the decisions. I got the news just like the
rest of y'all... :-)
steve
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
