Re: FW: Objective C vs. Java
Re: FW: Objective C vs. Java
- Subject: Re: FW: Objective C vs. Java
- From: email@hidden
- Date: Thu, 10 May 2001 11:58:47 -0700
>
> 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?
I'm going to leave the nuts-and-bolts of bashing Java to those more
qualified than me, but I can offer something of a response about the fact
that everyone on your team knows Java: they will THANK you for letting them
switch once they get to learn Objective-C. I've been learning Objective-C
in my spare time (which translates to about an hour sometime after midnight
after my kids are asleep and the kitchen is clean and the babies have been
fed and my wife has passed out) over the last two months and I already have
a bad case of Cocoa-using-objective-c-envy while I plug away at work. It
becomes apparent after a short time that Java is in many ways an
Objective-C wannabe - a less elgant knock-off-- and the Cocoa class
libraries got an awful lot of things right even if they aren't perfect and
the documentation is lacking. I stand by this even though I do muddle up my
objective-C code quite badly occassionally as I experiment and learn and
have been known to post my share of newbie-sounding questions.
I would think that, quite literally, if I were doing Objective-C full time,
it would take a few weeks to get productive and a few months to get fluent.
Someone with little or no programming experience would, of course, take
longer, but anyone with some programming and OOA/D experience under their
belt should take to this like fish to water...