Alternatives to WO
Alternatives to WO
- Subject: Alternatives to WO
- From: Jake MacMullin <email@hidden>
- Date: Thu, 01 Jul 2004 09:48:55 +1000
Having read that a number of people feel ready to "jump ship" is
disappointing. One of the things I value most highly about development
technologies is an active and vibrant developer community - and the WO
community is one of the best that I've encountered. It'd be a shame if our
numbers diminished.
However, a number of people have asked "What else is out there that is close
to WO"?
Until the other day, I was sure everyone else was way behind. I haven't come
across another product that matches WO in its elegance. There are ways of
building an architecture that has the best elements of WO from a combination
of open source Java projects:
Struts/Tapestry/Java Server Faces - in place of WebObjects Framework
(provide the separation of code from presentation, session management, etc)
Hibernate - Object/Relational Mapping layer
However, it takes *ages* to figure out how to put all the pieces together
and set up your IDEs and deployment to work with these technologies.
But, they *are* getting better. Sun have just released a product called
"Java Studio Creator" and in the few minutes I played with it - It looks
pretty good. The thing that impressed me most was that I installed it,
double clicked on the icon - and 5 minutes later I was running a simple
"Tell me your name and I'll say Hello to you" application. For me, this a
first in 'ease-of-use' for these traditionally complex Java technologies.
Granted, Java Studio Creator is only part the way to where WebObjects is, it
doesn't appear to make use of Hibernate (or any other ORM), but it *is*
catching up.
Personally, I think it would be a crying shame if Apple neglected to spend
the resources to keep WO at the cutting edge. Apple have said often that
they can't afford to let WebObjects die as they use it so much internally.
However, they don't seem to make much money from selling WebObjects.
Simple solution: Release WebObjects as Open Source.
You'd have a huge increase in the size of the development team, Apple would
benefit from improvements in WebObjects for their internal applications, and
the WebObjects community could take control of their own destiny - rather
than relying on Apple to realise what a great technology they're sitting on.
Regards,
Jake MacMullin
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.