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: Thomas Lachand-Robert <email@hidden>
- Date: Wed, 5 Dec 2001 19:03:34 +0100
Le mercredi 5 dicembre 2001, ` 06:24 , Matt Gough a icrit :
The point is that IMHO Apple will not have the luxury to maintain three
OSes and three frameworks in the future (unless it grows to more that 50%
of the PC market, something we hope all, but is a far away for now).
Obviously OS9 will be trashed (and I don't regret it, even though it has
a
more consistent interface than OS X), and OS X standard+server will
remain.
And for the three frameworks: Cocoa, Carbon, Java? Assuming than OS 9
disappear, I can't see the need to keep Carbon.
Here are a few good reasons just for starters (in no particular order)
PhotoShop, Microsoft Office, Illustrator, iMovie, iDVD, iTunes, Freehand,
Quark XPress, VectorWorks, Internet Explorer, AppleWorks, Acrobat,
FileMaker
Pro, MYOB, Virtual PC, CodeWarrior, (add your own examples here)...
Most of these apps will NEVER be ported to Cocoa, and for all of its
glories, there are no Cocoa apps in the same league of importance to Apple
as the above list. If push came to shove, which Framework do you think
they'd drop?
Matt Gough
Why do you say they will never be ported to Cocoa? Most of them would
highly benefit from Cocoa, and some of them are so buggy that they really
NEED to. Some will probably need to be rewritten from scratch, at least
for the interface, and choosing Cocoa would be a very good idea then. For
instance AppleWorks needs a lot of work in this field, and this work would
be much simpler using Cocoa. Also Acrobat 5.0 is so buggy I suspect the
interface would better be completely rewritten. The interface of XPress is
outdated, too.
Anyway, "never" in a very strong word in computer fields. Probably they
won't be rewritten in Cocoa in the next three years or so, I agree. But
after that? Most of these apps use Navigation Services now (except XPress)
, but they didn't three years ago.
Also keep in mind that Cocoa and Carbon can be mixed together, so it is
very possible to translate progressively an app. And thanks to Obj-C++ all
the model part doesn't need to be rewritten.
I believe that the main problem here is that most engineers in these huge
companies don't know Cocoa at all, and don't want or have time to take a
look at. (Some of them may be a little bit repelled by the strange syntax
of Obj-C, too.)
That's the main reason why I try to advocate it.
Thomas Lachand-Robert
********************** email@hidden
<< Et le chemin est long du projet ` la chose. >> Molihre, Tartuffe.