Anyways, my biggest concern with Rails is if it ponies up when I need to
write a more complex application.  I would rather not have to do trial and
error to find that out because right now I am "framework fried" after trying
both JSF and Tapestry and finding they both caused just as many headaches as
the time I was expecting to save.

For what it's worth, none of my green-haired kids (young Java experts)
are big fans of frameworks.  From their experiences, frameworks are
great for simple apps, but you wind up fighting the framework for more
complex apps.  At their recommendation, we do plain-old Model 2 JSP,
and we keep scripting in JSPs to an absolute minimum.  They'd rather
write HTML in the servlet and pass it along to the JSP than do Java in
their JSPs.  Seems reasonable to me.

Mike E.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].