To voice an argument that has not yet been raised in favor of not deprecating the NS formatter and making it a true wrapper around the Sun formatter...
WebObjects is all about the framework. I could care less that it currently runs on Java. I liked it better when it was Objective-C but I really was happy about the change in 2000 and didn't fight it. The potential of doing Java Webstart apps was just so compelling, SOAP, and other things. Now what about in 2010 when the language of the year happens to be C+- (... that's "C more or less"). That's not a real language, as far as I know, but we all know that things change over time and we might want to move the WO framework to a different development platform. Wouldn't it be nice if the formatting strings you used for the "WO framework" never had to change?. I'm saying whether they be hard coded or loaded at runtime from properties files or database attributes, it doesn't matter. The framework is what matters. I mean, c'mon. Why don't you just deprecate mutable and immutable Arrays, dicts, etc. Java sort of has those data structures too. Why duplicate the code? .... see what I mean? Where do you draw the line? When are we supposed to remember to use the NeXTSTEP class and when to use some Java or lang du jour class? WO, as a framework, is what matters. The language it runs on is just a vessel. -- Aaron
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
