From: Brad C. <bc...@vi...> - 2002-02-17 02:34:47
|
At 9:07 PM -0500 2/16/02, Anthony Eden wrote: >I suppose I just have a different opinion. I believe that it is best to >maintain mutability for the purpose of being more flexible as systems >change. The less I have to compile, the better. Yeah, reasonable minds can differ there. I've been on both sides over the years. Objective-C for example, ADDED dynamic typing to C of all things. But as a programmer, I don't object to compiling at all and experience with jakarta projects makes me equate mutablility with flexibility... as when pushing a rope. That's exactly why jwaa deals with entire websites statically. It was driving me nuts keeping all the stray bits straight with jsp and before that, perl. The whole flesibility argument has given me an abiding dislike for configuration "languages" as a solution to mutability/flesibility. There's a whole rant on this in one of the jwaa articles. Compile it with jikes and you get sensible error messages. Botch a configuration file and you get to debug exceptions from code you may not even have source for. -- Brad Cox, PhD; bc...@vi... 703 361 4751 o For industrial age goods there were checks and credit cards. For everything else there is http://virtualschool.edu/mybank o Java Interactive Learning Environment http://virtualschool.edu/jile o Java Web Application Architecture: http://virtualschool.edu/jwaa |