Re: FW: Objective C vs. Java
Re: FW: Objective C vs. Java
- Subject: Re: FW: Objective C vs. Java
- From: email@hidden
- Date: Fri, 11 May 2001 09:19:42 -0700
>
It's hard to argue with some of the points that a lot of the Objective-C
>
fans out there are bringing up about speed issues and loosely typed
>
objects/methods or whatnot. But you must also take in to consideration
>
the maintenance of the code and the ability to find people with skills
>
that will add to your project.
There is an old quote that Mac users love to pull out in the old Mac v. Win
wars. I don't remember the exact wording or who it's attributed to, but it
has to do with the fact that Cockroaches outnumber humans by an order of
magnitude, and that higher numbers do not note a higher intelligence.
The same can, perhaps, be said of this situation. Java is more popular - of
course. There are more Java programmers, and more resources for learning
Java. But none of this speaks to whether Java is better for developing
Cocoa applications. I have known Java for much, much longer than
Objective-C, but if you're going to program in Java - use Swing. If you're
going to program in Cocoa, use objective-C - it is much better suited to it
(the Java bridge is impressive, but there are unavoidable problems using
it). Why incur both the overhead of the Java virtual machine AND the
overhead of the Objective-c runtime engine?
Just my opinion, but since Apple has developed an Aqua PLAF, why not just
use Java if you prefer Java - then you have a program that can run on other
platforms. But if your desire is to target Cocoa primarily, you're better
off investing in Objective-C. Frankly, I think I have a better
understanding of Java now that I've begun to learn Objective-C, since the
design of Java was heavily influenced by Objective-C.
>
Don't hate me. This is my first post to the list :-( . I just want to
>
build Cocoa apps like everybody else here :-) - tyler
Nobody's going to hate you for holding an opinion, even if it is wrong =)