WebObjects 5.3 confused roadmap ?
WebObjects 5.3 confused roadmap ?
- Subject: WebObjects 5.3 confused roadmap ?
- From: Thibault <email@hidden>
- Date: Wed, 08 Jun 2005 10:37:24 +0100
Hello,
I know it's always a recurrent question every year but most of us are always
unhappy with the lack of a clear vision of the future of WebObjects since
many years. It's true it's hard to promote WebObjects as an Enterprise
solution when so little is clearly said by Apple.
However because WO still got a hard learning curve it's still a product for
engineer, not for everybody.
It might be obvious for all of us and giving WO for free should brings more
new developers. With new ideas. More experience in other areas. It's a very
very good thing.
So the WO community needs to help more the newbies and I'm please to see
this developer list helping them more and more. However I still think the
community still needs to provide more code examples (even if the ones you
can find here and here are high quality).
So the new 5.3 version is welcome.
I'm sure we're going to see more we services made with WebObjects powering
insanely great dashboard widgets.
For me saying "Java web application/service only on MOSX" is a non sense.
But saying "WebObjects web application/service only on MOSX" is not.
For me it just reinforce the idea that the cross platform and write once is
a myth. It never worked for us and it never applied for server-side
applications.
There is always a bit somewhere which block the other things. The problem I
found of those cross platform and write once solution is : they work but
they are not really powerful. Too much trade in/ trade out. Also I never
found those approach really helped us to develop a high quality code faster.
Again, especially for a web application/services.
However the object modelling approach worked very well.
For me Apple saying that "WO is for MOSX only" just means there is
absolutely no point of keeping Java as a main language.
Objective-C proved many time its superiority over Java and as a default
language for Cocoa applications it makes clear that WO should be using
Objective-C *again* (with or without Java, after all the bridge is still
there and rock solid).
About the deployment of WO5, the company I work for always used Windows
platform for two reason :
- JVM on Windows is really fast. Not that fast on MOSX.
- PC Servers are cheaper.
Now basically we need to use an Xserve for the deployment. Hum, the cost is
not going to help us. But I don't see the .war alternative as a confident
solution.
About the development, we were using Eclipse on windows but the fact we
never been able to use EOModeler properly always been a problem. So we end
up making them on the Mac. But Eclipse on the Mac never been really an
option when Xcode was a click away.
So I don't care to switch to Xcode as now it's seems really mature and our
new apps are in fact developed with Xcode since the beginning of the year.
I'm just trying to show that the best path for people without high skills is
to follow the path that the other already experienced.
>From my experience fighting with Eclipse on Windows, using obsolete tools
and having unnecessary problems just distract you too much to understand the
core of the WO frameworks.
I think without an engineer experience, you need to go where the
documentation and the examples are.
This way is today Xcode. You press the button and it works (well almost) and
you're concentrated on your code quality, not on something else.
It reminds me the most accomplished version of WO is still the 4.5 with
Objective-C and ODBC instead of Java/JDBC in terms of performances and
flexibility. But it's a kind of obsolete debate, isn't it?
The 5.2 is very robust and thanks to the Gigahertz, also fast.
I thanks Java for its "reassuring factor" : saying you're an Objective-C
developer do not attract as much as saying you're a Java developer on your
CV.
Yes I see a bright future for WO and I'm please to use the most reliable and
stable framework for web applications and web services I ever seen.
Sorry for having disturbed the main purpose of this mailing list : helping
people having code problems!
Thank you for reading.
Thibault
London, UK
Smile, we're still alive !
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden