On Sep 5, 2006, at 2:23 PM, King Chung Huang wrote:
On Sep 5, 2006, at 12:07 PM, Chuck Hill wrote:
- there are so many new cocoa technologies that we could use
(bindings, core graphics, ...)
One of the advantages of WO / Java is that it is cross platform.
Now, moving to Eclipse based tools, it is more cross platform than
it was looking recently. Tying it to Cocoa technologies would be
a step backward as a web platform. That said, I would love to see
EOF back in Obj-C for Cocoa applications!
I've heard this argument before, but I have a hard time
understanding how tying into Cocoa technologies would be a step
backwards as a web platform? After all, the platform that the
server software runs on doesn't dictate the client platform. Is it
a deployment advantage? Development advantage? I've never really
understood this.
The most important reason WebObjects should stay Java is the ability
to easily use other Java libraries on the server end. You're right -
it doesn't make a different to the client either way, but there are
hundreds of Java libraries people leverage on their WO servers.
Also, cross platform deployment is a pretty big deal to a lot of
people (although personally, we deploy 100% on xserve).
Ken
King Chung Huang
_______________________________________________
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/lists%
40anderhome.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]
