I have no desire to learn Cocoa. I don't like the Objective C, and
I don't believe it's a good idea for Apple to continue down the
path of what is essentially a dead language. I suspect I would give
up on my own Mac development efforts, and just concentrate on
creating embedded products, if I had to give up C++ (or D). And
note, just because there are ways to call Cocoa from C++ doesn't
mean I want to go to all the trouble.
I'm totally with you. Seems like, not that long ago, we took on the
huge task of Carbonizing our app framework and all our apps, because
it was the "future". Now, that future sure seems dead to me, complete
with burning cities and crying mutant orphans. We had plenty of
engineers to take on the Carbonization task without letting normal
development suffer. Now we don't. Do I have the time to completely
rewrite all our apps in a language that I'm uncomfortable with and
consider ugly and uneasy to read? No. Will we do it any way? Well of
course - we aren't gonna curl up and die just because Apple forgot
what they were doing before. It just means my job will no longer be
something that I look forward to doing every damned day.
Thanks, Apple, for having ADD and not asking us what we wanted. Love
the products (soft and hard), hate the direction (Cocoa) development
has gone.
I don't mean to disparage all the great work done by Apple's Carbon
engineers; I blame higher levels of management for lacking the
understanding and vision to ensure Carbon gets a proper commitment.
_______________________________________________
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
