On 10/5/07, Brian Pontarelli <[EMAIL PROTECTED]> wrote: > I guess my only fear is that S2 will become much more difficult to "get > into" when new users now have to understand multiple plugins just to get > an app up and running. The uber struts.jar solution helps to some > degree, but is just hiding the complexity, which once exposed (due to > core bugs, plugin bugs, plugin incompatibility, dependency conflicts, > etc, etc.) could alienate new users.
Personally, I'd be more concerned about alienating the volunteers who do the work. :) Here's the thing: A volunteer who has an itch to work on a JSP taglib may not have an itch to work on freemarker templates. There would not be a net gain of effort in favor of work on freemarker, only a net loss. In Apache circles, we have a saying: Let Darwin Decide. If pure JSP is a step in the wrong direction, then people won't use or maintain the taglib, and it will wither away. The point of a volunteer project like Struts is for us to create the framework that we each *want* to use to build our own applications. Organizations like Microsoft and Sun and Zend are already busily building frameworks for newbies to use. People (like us) choose to use frameworks like Struts because we provide a flexible core that we can each customize to meet our own needs. The solution to wooing newbies is documentation and examples. The omnibus struts.jar can provide all the components people need for a typical application, just like the struts-default configuration provides all the interceptors and results that people need to write a typical application. Unless someone goes looking for it, all the elegance and flexibility stays neatly hidden away. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
