Re: Anything new on the Horizon of Webobjects
Re: Anything new on the Horizon of Webobjects
- Subject: Re: Anything new on the Horizon of Webobjects
- From: petite_abeille <email@hidden>
- Date: Wed, 29 Oct 2003 13:55:49 +0100
While this thread has been midly entertaining so far, nobody has
answered James Hays original question:
"Anything new on the Horizon of Webobjects"?
Very disappointing :(
But was there anything else to expect from such a secretive
organization as Apple? This lack of communication could be construed in
three ways:
(A) Snobbism vis-a-vis their very own user base.
(B) Don't care one way or another.
(C) Don't have a clue in the first place.
In any case, here is my very own playful "Road Map" fantasy :)
(1) Migrate out of the Foundation legacy.
Most of what can be found in com.webobjects.foundation serves no
purpose whatsoever aside from ego inflation and intellectual
masturbation. Clumsily pretending to support ancient legacy projects is
not the way to go forward.
The time has come for WebObjects to bite the bullet and migrate to
java.util APIs. Implementing the relevant java.util interface on top of
the existing implementation would be a good start. There is no reason
for NSArray not to implement java.util.List. Neither for NSDictionary
to rudely snob java.util.Map. The same goes for NSComparator versus
java.lang.Comparable. And so on and so forth.
If something already exists in the core Java library, there is no
reason to reinvent it "just because". This applies as well to frivolous
pseudo features like NSData vs java.nio.Buffer, NSLog vs
java.util.logging, NSProperties vs java.util.prefs, WOTimer vs
java.util.Timer, WOHTTPConnection vs java.net.URLConnection, etc, etc,
etc...
(2) Migrate out of the NSBundle legacy
Nuff said, but deserves its very own bullet :)
(3) Migrate out of the AppKit legacy
It's time for WebObjects supporting cast of midly amusing clowns (PB,
EOModeler, WOBuilder & Co) to move out from the AppKit legacy. Move to
Swing or SWT. Better yet, provide integration with mainstream third
parties (e.g Eclipse and such).
(4) Reuse
Apple is a small company. WebObjects is a minor product. Its
development team fits in the cupboard of a small minivan. They cannot
do everything.
For instance, synchronization across multiple instance of WOApps is not
properly handled. Leveraging Java Message Service or other
communication toolkits (e.g. Javagroups) could help.
(5) Learn from others
Take a look at JBoss intelligent use of Java Management Extensions
instead of miserably roll your very own pathetic tool.
(6) Be creative
Get out more and see how things like ZeroConf's DNS Service Discovery
could fit in the picture.
(7) Wake up
Things have changed in the last decade. Time to innovate again. Get
over your nombrilistic self satisfaction.
"Technologies do age and it is hard mentally to keep up with others
when you were the greatest for so long"
-- Andrus Adamchik, March 1 2002
http://www.omnigroup.com/mailman/archive/webobjects-dev/2002-March/
020443.html
Cheers,
PA.
_______________________________________________
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.