On Mar 31, 2009, at 8:21 PM, Lachlan Deck wrote:
On 01/04/2009, at 6:29 AM, Mike Schrag wrote:
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.
The lack of power sucks,
Can you elaborate on the lack of power?
Things I love (not) about standard collections: can't instantiate
the silly things with objects. No nsarray kvc ops...
but the lack of immutable forms of the List/Map/Set interfaces in
Java is a failure IMO.
Indeed.
WO/EOF moving to straight List/Map/Set would suffer from a loss in
clarity as a result. On the flip side, it would gain the
performance and flexibility of the Java collections APIs, which is
a win. I'm definitely conflicted on the correct answer to this
conundrum.
As long as KVC options remain I guess I don't mind if they go the
way of the dodo. But I much prefer the clarity of setObjectForKey
than put etc.
Good Lord! I think we agree! :-P
Chuck
--
Chuck Hill Senior Consultant / VP Development
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 arch...@mail-archive.com
