I think this discussion is getting a bit off-topic in some respects.
As Eric has already mentioned, Obj-C/Cocoa is a fact of life for Mac
OS X development, so debating the merits of one programming language
and/or framework doesn't really change anything.
For those of us who develop using C/C++ and Carbon APIs, there are
valid concerns about the future of Carbon. In terms of its viability
to create usable software, the answer at this time is yes, since
there is no shortage of Carbon-based software out there. This does
not mean that Apple's application vision won't go through a future
paradigm shift that rules out the usage of a procedural API.
For the present, for app writers your 32-bit version should continue
to work just fine for the forseeable future. The issues in this case
seem to be that either there are cases where you're running into
issues due to the smaller address space for 32-bit apps; and/or from
a marketing point of view, the perception by end users that 64-bit is
always better so you need to show you have a 64-bit solution.
One area that concerns me, as a plug-in developer, is what happens
when a 64-bit version of the host application comes out. With the
Intel transition, we converted all of our plug-ins to Universal
Binaries and then everything worked just fine. With the 64-bit case,
I'm not sure what will happen, although my guess is that we're out of
luck. Rewriting everything in Cocoa will be a huge development task
for us, but maybe we can be done by 2009. :-)
For now, I'm very curious about what will be said in this afternoon's
HIToolbox session here at WWDC...
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden