Re: FW: Objective C vs. Java
Re: FW: Objective C vs. Java
- Subject: Re: FW: Objective C vs. Java
- From: Stefan Jung <email@hidden>
- Date: Thu, 10 May 2001 17:59:59 +0200
This was discussed at the email@hidden.
There is also an article at the BigNerdRanch.
While I am not very intimate with Java, I remember the following
statements:
The overall result was, ObjC is better.
No virtual machine - less memory - shorter load times
Native Environment instead of JavaBridge (There is an article at
www.cocoadevcentral.com about using the bridge) while the bridge
is not bad, it is either not very good.
In ObjC you can fall back to procedural programming when
helpful - try this with Java
Java has very strong types- half your code is conversion. Maybe
you are stuck at some time if you have a really big application,
grown beyond anything once was planned.
Speed? Slower most of the time, but some have shown Java being
faster in some cases.
The ObjC language is very simple, so it is easy to learn. If you
are familiar with C++, you have to rethink objects, because they
are completely dynamic in ObjC. This is only possible, because
ObjC lets you type loosely.
At WWDC a new book on Cocoa programming is released. I know the
old tutorials and ObjC manual and as far as I can see this book
is a faithful mixture of these old texts, updated to the new
Project Builder and Aqua. I think this book will use ObjC only.
So training new programmers may be easier with ObjC.
Also there is no bridge to Carbon. As Carbon and Cocoa differ in
features by now, it is well possible that you want a Carbon
feature. Though some people have already mixed ObjC and Java.
Stefan Jung
>
> "We" recently made a decision to develop a new application in
>
> Cocoa. This
>
> will be a significant product that will require development and
>
> maintenance for years to come. "I" am the fortunate individual
>
> who gets to
>
> do the initial development (no sarcasm - it's been years since
>
> I've worked
>
> on non-legacy code). My background is C and C++, and I'm looking
>
> forward
>
> to learning (a lot about) Java and/or Objective-C. Since we have
>
> no legacy
>
> code for this project, I get to do it right.
>
>
>
> Does anyone have any logical or illogical reasons to prefer Java or
>
> Objective-C for Cocoa development?
>
>
>
> From things I've seen and heard, I'm concerned about the following:
>
> Everyone (but me) knows Java, so it seems a good choice as far
>
> as finding
>
> more engineers in the future as the product gets bigger..
>
> Is Java _demonstrably_ less efficient than ObjC in MacOSX?
>
> This product will eventually connect to a back-end server that
>
> speaks HTTP
>
> and/or XML. Should this influence my decision?
>
>
>
> advthanksance, -kevin