In article
"Daniel Johnson"
> "Snit"
> news:C41B8841.B21D1%usenet@gallopinginsanity.com...
[snip]
> Certainly they may wish to add MegaGoodFeature (tm) to OS X, and it may be
> that this is a feature that Carbon can't support. But they can simply add it
> to Cocoa and not Carbon- problem solved.
>
> Indeed, they do that routinely. Cocoa Bindings are a simple example of a
> feature that Carbon *can't* do, but that didn't stop them implementing it.
Bindings, though, aren't a user-visible feature. If it's something more
like "We're planning to move the entire platform to multi-touch UI in
2011, and we can't/won't implement that on Carbon", then doing anything
possible to encourage developers to ditch Carbon as soon as possible
seems like a good idea. Because at that point it wouldn't be a matter of
Carbon developers not having access to some developer conveniences; it
would be a matter of Carbon apps not being able to take advantage of the
platform technology that, more than any other, set the platform apart.
(I'm not saying I necessarily expect Apple to move the entire platform
to multi-touch UI by 2011, of course; this is simply an example.)
--
"More than two decades later, it is hard to imagine the Revolutionary War coming
out any other way."
--George W. Bush in Martinsburg, W. Va., July 4, 2007