On Sep 4, 2006, at 1:04 AM, Georg Tuparev wrote:
On Aug 28, 2006, at 6:10 AM, Chuck Hill wrote:
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 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.
Chuck,
And how would you react if I we take into account that:
- most of us are more productive in ObjC
Yes, I was. At least on a line by line basis. But if I need a rules
engine, or an inverted index (Lucene) functionality, or a PDF
library, chances are that I will be more productive in Java as I can
just grab a well documented library.
- 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!
- many of us have large volumes of ObjC code
Still preferring Java?
As an overall more productive environment, yes. As a language and
core API, never!
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
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
