Pick the web framework you think is cool
Ever since I started adding additional web frameworks into AppFuse, people have asked me "which framework should I use?" I've often told them "use what you know." If you have in-house knowledge of Struts, use it. I thought this was good advice because I believed that existing knowledge leads to greater productivity.
Lately, I've started to change my philosophy. I'm starting to think it's more important to use the web framework you're passionate about. The one you want to learn more about. After reading Kathy Sierra's "Does it really matter if your tool is cool?", it seems this is a good idea. She writes:
Coolness (or just perceived coolness, it really doesn't matter) is linked to passion. The cooler you perceive your tools to be, the more passionate you are about those tools. And passion, while it might lead to the "everything is a nail" syndrome, has an extraordinary amount of value!
Obviously there's quality of life... a life with passion is certainly more fun than one without. And the more passion, the greater the chances that a person has what psychologists label optimal experiences. And the more optimal experiences one has, the more likely one is to describe life as being "happy". So, passion = optimal experiences = happiness. And research says happy people are generally more productive. Certainly they're more spirited and fun to be around...
So I guess passion leads to greater productivity, not existing knowledge. So which web framework do you think is cool? Which one are you passionate about?
If I had to choose based on my passionate choice, and the one that I think is the coolest, I'd have to go with Tapestry or possibly JSF (JSF would be a lot cooler if it let me put my JSPs in the WEB-INF directory instead of in the root). These are the frameworks I want to learn more about. 6 months from now? Maybe Laszlo or JDNC.
Posted by Glen Stampoultzis on December 10, 2004 at 12:29 AM MST #
Posted by thirdshift on December 10, 2004 at 02:32 AM MST #
Posted by Richard So on December 10, 2004 at 04:07 AM MST #
1 - Some people in the team (sometimes, most part of) aren't really passionated with their job
2 - The framework must allow to divide the effort in different and parallel tasks with less bottlenecks possibile
If I had to chose a framework for a team now, I would pick up Struts, since it is reasonalbly simple and a lot of guys know it. For my personal projects, I would probably choose JSF or Tapestry, just because I have a little esperience with them.
What about Velcity?
Posted by Filippo on December 10, 2004 at 08:50 AM MST #
Posted by Chuong Huynh on December 10, 2004 at 09:18 AM MST #
Posted by James on December 10, 2004 at 01:41 PM MST #
Posted by Matt Raible on December 10, 2004 at 01:48 PM MST #
Posted by Kris Thompson on December 10, 2004 at 05:24 PM MST #
Posted by Keith Donald on December 10, 2004 at 07:48 PM MST #
Posted by Robert Sfeir on December 10, 2004 at 07:53 PM MST #
Posted by Jason Baker on December 11, 2004 at 02:33 AM MST #
Posted by Robert Sfeir on December 11, 2004 at 07:27 PM MST #
Posted by Mats Henricson on December 11, 2004 at 10:32 PM MST #
Robert, yeap, Eclipse vs IDEA vs Netbeans vs vim vs blablablabla. Every time the discussion about what's cool happens, I just put on my headphones. :p
Posted by Jason Barker on December 12, 2004 at 05:06 AM MST #
Posted by MrTeacup on December 18, 2004 at 12:01 AM MST #
It would be Rails.
There are no words to describe the power and flexibility of a self-configuring framework. As they proudly claim on rubyonrails.org, there are less lines of code in some full-blown Rails-based app than in the XML configuration files required by your average Java framework... Very impressive... Although I was new to both Ruby and Rails, I was able to build a very functional application in a couple of hours, I had never had this feeling of instant gratification with any framework I've used before...
Hats off to all people involved in the making of this masterpiece... Long live Rails!
Posted by Xavier on December 19, 2004 at 08:59 PM MST #
Posted by Rick Hightower on January 02, 2005 at 10:15 AM MST #