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.
... this is what I meant -- UI, being a platform-specific thing, can
be done in ObjC or C#. The parts of the app that aren't specific to
platform (which should be the majority of it imho) should be coded in
C / C++ if there is any hope of making it work on other platforms.
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.
There are C# implementations for Mac (Mono, Portable .NET) but they're
in the same league as ObjC options for Windows (like gcc and
GNUStep). The gcc compiler has been able to do ObjC for a long time
now, but gcc usually isn't the compiler of choice on Windows -- Visual
Studio's compiler is. I wouldn't use straight GNU gcc if I were
compiling for a Mac -- I would use the version of gcc that Apple
includes with XCode (which includes things that the mainline GNU gcc
does not). Likewise, if i'm compiling for WIndows, I would use Visual
Studio, and Visual Studio doesn't do ObjC in any form.
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.
... I disagree, because if Apple wants to encourage more Windows
developers to port their apps to OSX (as i'm sure they do), the
Windows developers shouldn't be made to 'suffer' for the sake of the
Mac developers. I don't think ObjC is in any way 'suffering' (I
actually quite like it), but including C / C++ APIs (as well as ObjC)
for non-UI things helps WIndows (and *nix) developers who want to port
their apps to OSX.
I like (and prefer) Macs. Almost all of my development is done on my
24" iMac (at work) or my MacBook Pro and 23" Apple LCD (at home).
However, when I need to make sure my code will also run on Windows
(which is almost all of the time unless i'm doing platform-specific
stuff) or Linux, I need to choose a language that is well supported on
all platforms, which almost always means C++. Apple's gcc, GNU's gcc
and Visual Studio all support C++ quite well.
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