Was there any qualification on why each framework was chosen?

What I'm curious about is this: do devs use Tapestry only for their 
general, simple web applications? Or, are they/we willing to use it for 
deadline-oriented mission critical enterprise applications?

  - Mike





Konstantin Ignatyev <[EMAIL PROTECTED]> 
03/22/2006 10:50 AM
Please respond to
"Tapestry users" <tapestry-user@jakarta.apache.org>


To
TapestryUsers <tapestry-user@jakarta.apache.org>
cc

Subject
promoting Tapestry






                      Just want to share: 
 last night here at Seattle Java User group we had a  round table 
discussion where people were presenting WEB UI frameworks they use and 
tried to highlight things they love about them.  There were many: 
Millstone, Barracuda, echo2,  JSF, Struts, Tapestry, Tiles/Sitemesh, DWR, 
RubyOnRails
 Every presenter had about 6-8 minutes for a “sales pitch” and at the end 
people answered the question:
  If you were a king and decide what framework to use for next project, 
which framework will you use? (People voted once only for just one 
framework)

    Tapestry – 15;
Struts – 5;
JSF – 3;
 The rest got  zero or 1 votes;
    I could attribute Tapestry's warm reception to my presenter skills :)
but in reality it is the Howard's hard work and Tapestry community make 
the framework so appealing to developers.
  I ask everybody to speak about Tapestry more frequently on occasions and 
this way we all will benefit from wider Tapestry adoption. 
 

Konstantin Ignatyev




PS: If this is a typical day on planet earth, humans will add fifteen 
million tons of carbon to the atmosphere, destroy 115 square miles of 
tropical rainforest, create seventy-two miles of desert, eliminate between 
forty to one hundred species, erode seventy-one million tons of topsoil, 
add 2,700 tons of CFCs to the stratosphere, and increase their population 
by 263,000

Bowers, C.A.  The Culture of Denial:  Why the Environmental Movement Needs 
a Strategy for Reforming Universities and Public Schools.  New York: State 
University of New York Press, 1997: (4) (5) (p.206)

Reply via email to