I'd absolutely use it for a new project. Especially for web or Java
Client applications. But for Cocoa....
How are you going to hook the two together? Not that you can't, but
the Java-Cocoa bridge is long gone. Is there a reason you don't want
to use a Java Client?
Dave
On Apr 15, 2008, at 3:25 PM, Nolan Whitaker wrote:
Hello.
First off, let me say that I absolutely love what Apple has done
with Cocoa.
(I owned a NeXTStation '040 back in the mid 1990s and now wish I had
done more software development with it instead of trading it for a
Sun Sparc 5,
but hindsight is 20/20. )
I'm in the process of working up an idea for a client/server
application that will
have a rich front end written in Cocoa as well as a web-based front
end.
Most, if not all, of the server-based portion of the application
will be
written in Java.
When Web Objects first appeared, the Java API was rather sparse.
There wasn't support for a number of classes that exist now, and
using WOs
made a lot sense. Given that I am already familiar with Cocoa
classes,
using WOs still makes some sense given that it implements many of
the Cocoa
classes that I am familiar using and makes database access a little
easier.
My question is this, given the rich API that Java offers today, why
should I use
Web Objects on a new project?
Thanks in advance,
Nolan Whitaker
http://www.NolanWhitaker.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
