Re: Mixing Obj-C & Java in same Cocoa app?
Re: Mixing Obj-C & Java in same Cocoa app?
- Subject: Re: Mixing Obj-C & Java in same Cocoa app?
- From: Ondra Cada <email@hidden>
- Date: Fri, 14 Sep 2001 22:39:08 +0200
Finlay,
>
>>>>> Finlay Dobbie (FD) wrote at Fri, 14 Sep 2001 20:38:30 +0100:
FD> Java will always be slower than Obj-C, that's kind of due to underlying
FD> architectural differences that can't be changed without a complete
FD> retooling of Java, and in the process fundamentally changing the goals
FD> of the API.
Actually, although _I don't know Java that good_, I guess that
(a) with compiled Java/Cocoa (!forget swing!), there should be a very little
penalty over ObjC (actually, the only two reasons I see for compiled Java
being slower is the GC, and perhaps that Java does not support structs, so
things like NSRect have to be objects; none of them should be that
important);
(b) with GNU C, it would be relatively easy to support compiled Java in the
Cocoa environment.
I personally guess that the word is "There is no reason, since Java is not a
primary Cocoa language, only a compatibility tool". By other words
- if you want the thing to run in other Java environments, you have to use
SWING and consider its slowness anyway;
- if you don't need this kind of portability, just use ObjC/Cocoa and forget
the Java thing.
This is just my own advice though and might be ways out of what Apple thinks!
---
Ondra Cada
OCSoftware: email@hidden
http://www.ocs.cz
private email@hidden
http://www.ocs.cz/oc