On Mar 22, 2007, at 08:12:39, Frederick Cheung wrote:
My point was that you can spend a day or two and be comfortable
with the syntax of Obj-C, it's not a huge language in the way that C
++ is ( I did it back at wwdc 2004, there was a nice pre -
conference session on cocoa for beginners) but becoming proficient
with the Carbon API is not a one day job (and neither is Cocoa, but
the point was that I don't think the language itself should be such
a stumbling block)
Then our brains work totally differently. I spent a couple weeks
trying to learn Obj-C and Cocoa near the beginning of its life on the
Mac, writing a calculator. By the end of that time, I was still
finding myself forgetting to start calls with the [ and having to
option-leftarrow back and add it. Even now when I'm required to use
Cocoa to add some new functionality, Obj-C is still a hurdle for me.
A day or two? Hardly. It's akin to having to type the English
language, only using a completely new set of punctuation rules. !I!
what I mean? One might assume (gasp) that you - being able to
completely absorb a new programming language in a day or two, could
also learn to speak a foreign language. For me and many others, it's
not easy at all. French, German, I tried them both. The only
difference here is that my job requires that, if I want to keep up
with technology, I must now speak Obj-C.
If I could turn back time, I'd like to be at the first Obj-C
discussions, pound my fists on the table, and request that, since
it's built on C and C++, they use the existing C and C++ language
rules. I can't think of any reason why [[NSAutoreleasePool alloc]
init] is any better than NSAutoreleasePool::alloc()->init(). That's
really the part that makes me crabby. I have no beef with Cocoa other
than that I must type it in Obj-C.
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