Am 01.04.2009 um 06:00 schrieb Hugi Thordarson:
That being said, I still believe WO should go the Java way with collections :). I know the foundation classes rulezinate and roxxxorz, but we're using the language, so we should be embracing it and it's conventions - besides, proprietary stuff scares potential users away. I now try to use the standard java collections where possible, and they're not so bad once you get used to them.
You can argue about this stuff until you're blue in the face... fact is all "efforts" to "fix" using java collections only break old code and make it harder to read and debug. It's not really helpful to have an API that half uses java collections, half NSArray. It's also not useful to redo NS* as interfaces as it will break a ton of code for no gain whatsoever.
Imagine having NSList and NSMutableList which extend List! Wow, great move! Except that these would still be mutable, still feel weird. The real failure was made 8 years ago during the java-only conversion, there is nothing reasonable one can do now to fix it.
One *could* try to make less of a mess with more thinking, though. Cheers, Anjo _______________________________________________ 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
