Re: WO in Java or Objective-C

[Ricardo Strausz]

Hola Chuck, Ashley y Dana! On Aug 28, 2006, at 12:06 AM, [EMAIL PROTECTED] wrote: Message: 12 Date: Sun, 27 Aug 2006 21:10:51 -0700 From: Chuck Hill <[EMAIL PROTECTED]> Subject: Re: WO in Java or Objective-C (Was Re: Is WebObjects 4.5 going open source?) On Aug 27, 2006, at 9:04 PM, Ashley Aitken wrote: WO in Java or Objective-C?  What would be most sensible going forward? Given that there is a lot of enterprise Java code out there that WO   in Java can and does take advantage of (e.g. as it now uses JDBC to   replace the need for custom adaptors).  Given that WO in Objective-  C would require adaptors to be written for all the required   databases (this was a sticking point somewhat for WO when it was in   Objective-C) ODBC can replace the generic JDBC. Of course, I know that Objective-C is a much more powerful language   (with categories and the like) but Java does have some things going   for it as well (e.g. portability).  Also if WO went back to   Objective-C it could once again use Apple's development tools,   whereas it would not be possible to use all the great Java   functionality in Eclipse. I do not feel any problem with the tools... I was used to emacs-type programming. Personally, I feel that given all the improvements (and yes there   were some steps backwards) that Apple has made to WO (especially   EOF) since WO4.5 and Java's enterprise connections (and recent   language improvements) and ability to deploy in Servlet containers   etc) that it would be best to stay with WO in Java (e.g. if   implementing a new open source WO). I would only like to see something like EOF in Objective-C... the rest can/most stay in Java. I quite like Objective-C as a language.  I much prefer it to Java.    That said, moving WO back to Obj-C is nothing something I would be in   favour of.  There are just too many 3rd party libraries in Java. I agree... in both: Objective-C is preferable language, and WO, as a unit, most stay in Java in order to be truly platform independent and to include all those libraries out there... but, since there will be no more bridge, some of us will need some kind of EOAccess layer into OSX... an ODBC adaptor for Core Data would be enough for me... BTW What we will happen with Java Client? Is it possible to code a JC app with WOLisp? How do you design interfaces in pure Java? I will miss also the Interface Builder test-mode... or not? Dino   Chuck

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to archive@mail-archive.com