• 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: Objective C and C++
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Objective C and C++


  • Subject: Re: Objective C and C++
  • From: Brian Willoughby <email@hidden>
  • Date: Wed, 24 Dec 2008 15:54:36 -0800

First of all, if you'd learn ObjC thoroughly, you'd realize that you don't need to write that much code compared to other languages. So writing it twice would not exactly be double the effort. Plus, it's generally the UI which needs to be written in ObjC, and you can't write AppKit code on Windows, not even in C#, so you're stuck with writing the UI code twice anyway unless you choose a 3rd party option.

Second, Apple hasn't really made ObjC proprietary. There are ObjC compilers for Windows, and the language itself is open source. You could, with some effort, get ObjC working in your Windows app. In contrast, I am not aware of C# being available for any other platform, much less being open source.

Besides, none of Apple's examples are geared towards cross-platform development anyway, so forcing the Mac developers to suffer for the sake of the Windows developers doesn't make much sense as an argument.

Brian Willoughby
Sound Consulting


On Dec 24, 2008, at 14:15, John Michael Zorko wrote:

The most important thing Apple should do is create sample *Cocoa*
applications - not command line ones. This way, they could explain how
audio is supposed to run as a background thread that can be
interrupted by a UI control.

I suspect that they simply didn't want to create special projects for
Cocoa and Carbon, but since Carbon is officially a dead end, why not
make all example Cocoa-only?

Well, I for one am glad that Apple continues to provide examples in C+ + (read: non-ObjC). Many (if not most) of us have to make our apps work on Mac OSX and that other platform -- you know, the one with the 90%+ market-share called Windows. Writing all of the code twice (once in ObjC and once in C#) is just _not_ an option most of the time, so i'm quite thankful, as a full-time cross-platform developer, that I can code 90% or more of my app in C++, and only the platform-specific bits in ObjC or C#. ObjC is a cool language, I completely agree (the more I do it, the more I enjoy it) -- but so is C#, and when each camp demands that we drink their Kool-Aid, those of us who have to code for _both_ are really turned off. C++ is not the greatest language ever, but it's a very good object-oriented language to do professional cross- platform work in.


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Objective C and C++
      • From: John Michael Zorko <email@hidden>
References: 
 >Objective C and C++ (From: Brian Hughes <email@hidden>)
 >Re: Objective C and C++ (From: Marc Vaillant <email@hidden>)
 >Re: Objective C and C++ (From: NickMtl <email@hidden>)
 >Re: Objective C and C++ (From: Brian Willoughby <email@hidden>)
 >Re: Objective C and C++ (From: Brian Willoughby <email@hidden>)
 >Re: Objective C and C++ (From: Kevin Boyce <email@hidden>)
 >Re: Objective C and C++ (From: NickMtl <email@hidden>)
 >Re: Objective C and C++ (From: John Michael Zorko <email@hidden>)

  • Prev by Date: Re: Objective C and C++
  • Next by Date: Re: Objective C and C++
  • Previous by thread: Re: Objective C and C++
  • Next by thread: Re: Objective C and C++
  • Index(es):
    • Date
    • Thread