Re: ObjC++ (and a word about Java, too ;-)
Re: ObjC++ (and a word about Java, too ;-)
- Subject: Re: ObjC++ (and a word about Java, too ;-)
- From: email@hidden
- Date: Wed, 5 Dec 2001 12:16:53 +0100
Le mercredi 5 dicembre 2001, ` 09:34 , Smith, Bradley a icrit :
Could it be that Apple don't really want you to use it? I suspect it's
there
for those that are desperate but I don't think they want the avargae Cocoa
developer to think "Oh cool! Obj-C++. I'll use that then!". Of course I
may
be wrong.
Brad
My guess is that there are different people with different opinions about
that at Apple, like on this list ;-) But it is probably not a high
priority at Apple, since they took a long time before resurecting Obj-C++.
Probably there are just overloaded, with three OSes, four platforms, five
programming languages, adozen of apps, plus all the hardware... (There is
a french proverb: "Qui trop embrasse mal itreint", which can be translated
approximately: "Who embrace too much doesn't hug well").
Anyway it is obvious TO ME that Obj-C++ is an important advantage for
Apple / Mac OS X, so I advocate it. I strongly believe that Carbon is just
a dead end (even though it is badly required now, due to the large
quantity of existing Classic code).
So Cocoa is the future. On the other hand, it is just too much asking to
most people, especially whose doing cross-platform development, to program
everything in C or even Obj-C. So the modelling part of the programs can
be done in C++ (this is usually already done), and only the interface has
to be in Obj-C; both fit together nicely with Obj-C++, thanks to the fact
there are very different extensions to C. This makes plain sense since the
interface should always be rewamped for every target system (instead of
doing a poor port as we see sometimes), and there is already a lot of
things that Cocoa does autmagically, so it is not a huge work.
Note that I wouldn't need Obj-C++ so often if Obj-C would implement some
of the nice features of C++ I feel very useful: namespaces, declarations
everywhere (it's in C99), function overloading.
I somehow feel that there is a lot of people at Apple (and elsewhere)
believing that Java is the best approach to cross-platform development. I
used to believe that, too, but now I changed my mind. I tried for months
to have a good app in java. It worked, but I was not satisfied:
- it was a computational intensive app, and in that field Java is slow and
notational-inconvenient;
- it was not really a true Cocoa app (even though I used Cocoa-Java, not
Swing); there was minor differences with standard apps, I just hate that;
- there was some strange bugs in the frameworks, in the compiler, etc.
- Java is not intended to develop apps, there is a lot of strong
limitations making perfect sense for applets and just irritating for apps.
Moreover Microsoft is trying to kill Java. It's basically in the same
situation than Netscape Navigator six years ago.
Now I use Cocoa with Obj-C and I feel GOOD. I still hate the brackets
(difficult to type on a french keyboard), but otherwise it is great. I
would never have realized that if I haven't tried.
So here is my advice to every people using Java on this list: try to use
Obj-C instead (except for network or Internet based apps). You will have a
faster app, a better framework, a much simpler and cleaner language, and
worse docs (oops, sorry, couldn't resist).
Thomas Lachand-Robert
********************** email@hidden
<< Et le chemin est long du projet ` la chose. >> Molihre, Tartuffe.
| References: | |
| | >RE: ObjC++ (From: "Smith, Bradley" <email@hidden>) |