Edwards, Waverly (21/6/07, 15:39) said:
>Of course if there is not enough participation, we
>might just be giving Apple the bullet to the gun they are pointing at
>us.
My personal opinion is that:
1. Apple needs to unify or rationalize Carbon and Cocoa in order to
eliminate duplicate APIs. The current situation is not good for users
(inconsistent UI and behaviour) or developers (problems trying to mix
incompatible window and view systems). The argument for unifying Carbon
and Cocoa was apparently lost some years ago (see Ed Voas' emails to
this list in 2004), so the only thing left is for Apple to rationalize
the situation by removing APIs.
2. Apple have handled this badly. Pulling 64-bit Carbon APIs that were
previously included in beta versions (and promised at WWDC 2006) is
disrespectful to developers who have been developing for these APIs. The
minimum that Apple should do is to restore these APIs (and maybe
deprecate them for the successor to Leopard).
I wouldn't sign a petition, though. What is the petition for? I don't
think Apple can continue with the current status quo (point 1, above),
and the company I work for is not depending on 64-bit Carbon APIs in
Leopard (point 2).
Jeremy
_______________________________________________
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
This email sent to email@hidden
