Re: xcode-->java-->cocoa - how long? how many?
Re: xcode-->java-->cocoa - how long? how many?
- Subject: Re: xcode-->java-->cocoa - how long? how many?
- From: Jeff Pritchard <email@hidden>
- Date: Tue, 14 Jun 2005 16:52:26 -0700
Thanks Charlton,
The main reason I chose it is that I've had my fill of "C dolled up
to pretend it's object oriented". In all fairness I haven't tried to
learn objective C, so maybe it's not as painful as other things I've
seen. At work (Qualcomm) I have to use the painful quasi-object-
oriented C flavor adopted by BREW. It's enough to make you weep. I
just thought by using a language that was object oriented from the
ground up it might flow a bit better and be less frustrating to
separate it mentally from the other programming I do.
best,
jp
On Jun 14, 2005, at 1:20 PM, Charlton Wilbur wrote:
On Jun 14, 2005, at 3:56 PM, Jeff Pritchard wrote:
I was just wondering how long Java cocoa development has been an
option, and wondering if I'm an extreme minority at this point,
with very few developers using java for cocoa development yet. If
not many, is it just because it's new, or are there some
substantial downsides to using java for cocoa?
What it really comes down to is that if you're doing cross-platform
development, you're likely to be better off using Swing, and if
you're doing Mac-only development, you're likely to be better off
using Objective-C. Cocoa really is designed to work well with
Objective-C, and it's not such a great fit for Java.
Out of curiosity, why are you using Java instead of Objective-C?
Charlton
--
Charlton Wilbur
email@hidden
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden