JA-SIG Keynote: Comparing Java Web Frameworks
This morning I did my first keynote at the JA-SIG Summer Conference in Denver. My talk was on Comparing Java Web Frameworks. I told attendees I'd post it here afterwards, so here it is:
Download Comparing Java Web Frameworks Presentation (1.1 MB)In addition, I mentioned my Java Web Frameworks Sweetspots Whitepaper.
Will I be comparing web frameworks at conferences for the rest of my life? Possibly. I've been submitting 2-3 proposals to conferences and it's the only one that keeps getting selected. I'll be delivering it at OSCON, JavaZone, Colorado Software Summit and ApacheCon US.
The Colorado Software Summit wants to have an original presentation - so I may need to drop a framework or two and add in Seam, Grails and GWT. If you are planning on attending one of these talks, which frameworks would you like to see compared?
Related: Comments after I delivered this presentation at ApacheCon EU.
Posted by Sanjiv Jivan on June 26, 2007 at 06:07 PM MDT #
Posted by Yuccaplant on June 27, 2007 at 06:54 AM MDT #
Posted by Angsuman Chakraborty on July 02, 2007 at 03:55 PM MDT #
Posted by sudhir nimavat on July 04, 2007 at 04:52 AM MDT #
Posted by Rosh on July 11, 2007 at 02:50 PM MDT #
Rosh - I don't have an opinion about the ZK framework because I've never used it or had any demand from clients. The good news is I do plan on attacking Comparing Java Web Frameworks from a couple of new angles in the future:
For #1, I hope to figure out what's important to developers and companies when choosing an open source web framework. I believe the underlying technology is only part of the equation - project health and stability tend to be more important to companies long-term. For #2, I hope to talk about other frameworks that run on the JVM - for example, GWT, JRuby on Rails, Grails, OpenLaszlo (and possibly Flex).
Also, as part of #1, I think it's possible to divide all web frameworks into 3 categories: request based (Spring MVC, Struts 2), component based (Tapestry, Wicket) and RIA (GWT and OpenLazlso). As part of the choosing, you decide what your needs are (of the 3 categories) and then start drilling down from there. I think this will allow a deeper analysis of the different categories and the easier addition/elimination of frameworks based on the important criteria (#1). For example, if a company has a constraint like they have to support non-Javascript browsers, does it make sense to use GWT? Probably not.
Posted by Matt Raible on July 11, 2007 at 02:58 PM MDT #
Posted by Jim Tolson on July 25, 2007 at 06:08 PM MDT #
Posted by Jason E. Shao on October 31, 2007 at 12:30 PM MDT #
Posted by chzh on March 25, 2008 at 03:43 AM MDT #