You guys are scaring me. I'm reading this and the "64-bit Carbon"
thread and wondering if I missed some news?
All I see is that Carbon will not be 64-bit in Leopard.
Why do I need 64-bit? Things are working pretty smoothly in 32-bit
Universal.
Is there some other kind of announcement I missed?
Has all further Carbon development at Apple been stopped?
Is Carbon support being dropped? Now or at some future announced
date?
Yes, I have spent the last two years learning Carbon and basically
rewriting a lot of code using Quartz and HIView. Would I be
pissed if this was no longer going to be supported? You bet!
But, I'm basically happy with Carbon the way it is and hope it has
a long shelf life. Did I miss something? Am I delusional?
I wish someone from Apple would make a definitive statement about
the future of Carbon, so instead of guessing and panicking we would
at least know where we stand. These are business decisions that
have very real costs. Having the rug pulled out could be crippling.
So, what is the simple answer to the subject of this thread??
Is Carbon Viable?
If I am current on 32-bit Universal and not using any deprecated
functions(well almost), what kind of shelf life could I expect?
Even if that requires moderate updates, if I am at least able to
continue to build and ship my product on Macintosh I would consider
that viable.
It really all depends on what you need and what you want to be able
to do. Apple had already said that the latest and greatest new stuff
is going to be Cocoa-only, so to access it you have to call Cocoa
from within your Carbon application. If you need 64-bit then you're
obviously screwed. But the real concern is the very clear message
here that Carbon has been demoted to being less than a 1st class
citizen for Mac development at best, and is on the way to joining
classic on the technological grave yard at worst.
Any point on that spectrum is a concern to anyone writing Carbon
applications. If all this means that your application will eventually
need to be Cocoa to be a competitive product (and it sure sounds that
way for a lot of people), then time and resources invested in further
Carbon development tend to look like a waste since you're going to
have to redo much of it later anyway. That doesn't leave you with any
real good options, and all paths lead to porting your application to
Cocoa, which is not attractive to a lot of people who have already
spent too much time porting from classic to Carbon, old-style windows
to HIView, CW to Xcode, and PowerPC to Intel.
Larry
_______________________________________________
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
