• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Apple and Developers (was lots of different subjects)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apple and Developers (was lots of different subjects)


  • Subject: Re: Apple and Developers (was lots of different subjects)
  • From: Rainer Brockerhoff <email@hidden>
  • Date: Sun, 24 Mar 2002 12:23:18 -0300

>Date: Sun, 24 Mar 2002 01:07:02 -0500
>From: "Andrew R. Mitchell" <email@hidden>
>Subject: Apple and Developers (was lots of different subjects)
>...
>I've been following the Cocoa Advocacy/Cocoa's Popularity thread for
>days now, and after todays messages I just had to chime in. I'm not
>trying to start a flame war here, I'm just trying to provide some
>perspective from a long time Mac (now Carbon) developer.

As a Mac developer since 1984 (and on other hardware since 1969), allow me to add a few comments...


>First off, I'm tired of this Carbon vs Cocoa, Objective-C vs C++
>flame war that is going on. Both Carbon and Cocoa are key for the
>future success of Apple. And neither is perfect for everything. API
>choice along with language choice should be based on the task at
>hand. Some things Cocoa is better for, some things Carbon is better
>for. Some things C++ is better for, some things Objective-C is better
>for, and lets not forget some things an alternate language may be
>better for (AppleScript, Java, Ada, Smalltalk, Dylan, Perl, Python,
>etc). Not every language or API is suited for every task.

I couldn't agree more. Although I'm in the (perhaps) enviable position of not having to port an older application to run under the Carbon event/GUI models, my Cocoa applications rely heavily on calling into Carbon frameworks (yes, and BSD too). I expect this will continue for the life of Mac OS X.


>Once you get by our differences, the rest of the problems we have
>with Apple seem to be fairly consistent between us. They can be
>broken down into the following eight primary issues:
>...

Great summary, Andrew!


>7) Cost - Some of us are professional developers, some of us are
>hobbyists, and some of us fall somewhere in between. Apple needs to
>make sure we all have the ability to make great software for the
>platform. (One of my requests would be to have WWDC webcast.)

Let me add here that, as much as I like WWDC and Apple's developer support, the rising costs are making it increasingly prohibitive for small developers, especially small non-US developers like myself. Webcasting WWDC would be no solution either... we just can't get at the bandwidth. Selling the DVDs a month or two later, at media+shipping cost, might help some, although in the current format the most important parts (sample code and text screens) are unreadable.



--
Rainer Brockerhoff <email@hidden>
Belo Horizonte, Brazil
"I love deadlines. I love the whooshing noise they make as they go by" (Douglas Adams)
http://www.brockerhoff.net/ (updated Feb. 2002)
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Need advice on OpenGLView behaving like a control
  • Next by Date: Re: OpenGL and Document-Based Cocoa app
  • Previous by thread: Re: Apple and Developers (was lots of different subjects) (rekindling the fire)
  • Next by thread: Re: Apple and Developers (was lots of different subjects)
  • Index(es):
    • Date
    • Thread