On Mar 31, 2009, at 12:27 PM, Hugi Thordarson wrote:
Heh - and while we're at it, let's replace NSArray with
ArrayList, NSDictionary with HashMap and NSSet with .... well,
some of those gazillion java collection classes....
This already should have happened. Once you get a firm grasp of
the Java Collections API, it's design, intention and power,
NSArray and it's company will make you want to puke. I actually
thought that WO would move in this direction by first making
NSArray implement List, and do all the similar stuff, then
depreciate Foundation collections, and the finally get rid of
them. Well, maybe that still is the intention, but it sure is slow.
Agreed. Foundation collections are an embarrassing relic.
Unfortunately, the standard Java collection classes (JCC) gloss over
an important aspect of collection classes: mutability vs.
immutability. EOF requires the latter for all attributes, so
switching to JCC in EOF would be dangerous, and, IMHO, foolish.
AFAIK, the only benefit to using standard JCC is to be more
"standard" Java... something I'd like but am willing live without in
order to gain the benefit of EOF.
Furthermore, IMHO, the standard JCC are more embarrassing than the WO
ones. How many redesigns have the standard JCC had? How many
redesigns have the WO ones had? Certainly the WO design has stood
the test of time, and the Java ones have not. And we still have
Liskov-violating crap like java.util.Properties.
sacha
--
Sacha Michel Mallais Senior Developer / President
Global Village Consulting Inc. http://www.global-village.net/
PGP Key ID: 7D757B65 AIM: smallais
"The bird of paradise alights only upon the hand that does not
grasp." -- John Berry
_______________________________________________
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 arch...@mail-archive.com
