On Sunday 23 June 2002 09:55 pm, Pete Carapetyan wrote: > If you want software re-use, make Avalon consistent, as simple as > possible, provide less rather than more documentation, and tight > coupling becomes avoidable. We all win. Except maybe the perfectionists, > who want to keep making it more perfect. <snip/> > imperfect, and battle forever. But that is not the case. Nail it down > and keep it consistent - we got some friggin geniuses working on it here > already. Perfection would probably come anyway.
+1! Avalon evolves. When it was mentioned that a tomcat developer disliked avalon because there are always code changes when upgrading. Two responses: 1) Its a framework, frameworks evolve 2) When you pick a version, an upgrade is not required. The Avalon project produces very high quality code (from my experience) Thus you are rarely, if ever, forced to move on. Of course Avalon is a drug and you'll want more, but its not *our* fault that we have addictive patterns. -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
