Related to the ! thread, but a more general concept that I want to bring up and underscore. This is my mini manifesto on why we can't treat the default options and settings in Struts lightly. These are all my opinions, but I think they are also fairly common sense.
Goal: It should be our goal to ship Struts in a way that it is pre-configured with default settings that mimic the agreed upon styles and techniques by the very best Struts users and developers. This is critically important. Suppose we ship struts with all sorts of options turned off by default, but the core set of developers turn those options off in all our apps. What will happen is that the user base, who generally will not change the defaults, will use Struts under different constraints than the developers. A disconnected will form, and the users will push for changes that the developers will not understand or see in their daily development. We should tread very carefully whenever we talk about options and switches and say, "well don't worry, they can turn it on if they want". If every developer is in agreement, then it is fine. But if, say, Ted or Don or Patrick doesn't agree, we need to really dig in to the heart of the issue. Because odds are that what is happening is that two very different styles of development are happening by different team members, and therefore the product isn't being optimized due to competing interests. --------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=41361&messageID=82485#82485 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
