| |||
| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
Since I was responsible for the begning of this heated debate (not intentionally, of course), I'd like to contribute my point of view, and again ask for help. But first let me summarize the thread so far: Deric mentioned 100 messages, but I 've been reading an saving each one of them and, unless my pop server is way too lagged behind, It's exactly 69, as of this reply. Either way it's a lot of messages... Of these, only 3 really addressed my problem: Eric's doom statement that I must learn obj-C; Mike's suggestion to focus more on other aspects of the meeting. Both quite useful messages (thank you both); and yes Deric, I'll be knocking on your mail box soon. I also particularly like Larry's assessment of the implications for the average Carbon developer, when he says that: "... . My main concern with Cocoa is the same as it is with any large, comprehensive framework: Its default behaviors are trivial to get, and anything else requires significant effort to understand the framework well enough to figure out how to get the nonstandard behavior you want, and in some cases you end up fighting the framework to get that behavior." I think this summarizes very well the way I see the whole issue. Everytime I decide to learn some new programming technology (and I love to learn them) I feel that unless I dig deep and really understand all the ins and outs of an API, framework, language, or whatever, and unless I can go beyond the trivial, I'll eventually endup in a dead end. And that kind of learning takes a lot of time and effort. Like Larry said, the trivial only gets you so far. So I tend to 'pick my battles' very carefuly... I'm obviously no expert Mac developer, but my language of choice is C++, which I know fairly well ( even teach in some basic classes in) and I'd say I know Carbon, at least I got to the point where I understand and use the main concepts (Carbon events, HIViews, etc.) without too much effort right now. So a while ago I decided to start a new application, and after a long term of reading, experimenting and learning, I felt confident enough to embrace a very challenging (for me) project, which is taking up every minute of my (scarce) free time: a comercial application using Carbon. I work alone and can only count on me (and on the great voluntary help I've gotten from this list). At this point, What should I do then, drop everything I leaned about Carbon, learn another language/framework and start all over again? Well I've already come to terms with the fact that I have to learn ObjC. Actually I am printing some material right now so I can read when I'm away from my Mac. But I am affraid of not being able to get proficient enough in language and in Cocoa before June 7th, while getting at least to an alpha of my Carbon application, in order to really make WWDC worth every peny I'd be spending. After all my main reason to go is to improve my knowledge of the platform so I can do a better job of my (right now Carbon) application. So I guess my original question sill stands (and I promisse that, even if I get no replies I'll shut up...): Given the Conference's announced content, does anyone have a sugestion of how to maximize the benefits of a, lets say, intermediate Carbon developer going to San Francisco in June? Dr. Carlos Eduardo Mello (email@hidden) Music Technology Lab, Music Department University of Brasília, Brazil |
_______________________________________________ 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 This email sent to email@hidden
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.
