There is no "best" web framework

Prev

. . In embracing the diversity of human beings, we will find a sure way to true happiness.

Can this thinking be applied to web frameworks as well? What if it's not about choosing the best framework for your type of application? http://raibledesigns.com/rd/entry/choosing_a_jvm_web_framework What if it's all personality related?

documented on: 2008/02/06, by Matt Raible

There is no "best" web framework

Makes sense — it would explain why so many web frameworks are less about the technology than the cult of personality around the lead developer (Tapestry, Rails, etc.) It would also explain the vast proliferation of frameworks that all function more or less the same way.

It amuses me that we may have reached the point in this well-worn area where it becomes about personality instead of technical merit.

Ben replied on Wed, 2008/02/06

There is no "best" web framework

I think is very very interesting to have several "coding/development styles" because the development style selected has a strong influence in your web application architecture.

There are many frameworks but not so many development styles. I like to classify web frameworks in these categories (frameworks cited are examples, this is not an exhaustive list, DWR = DWR + some JavaScript framework):

Client/JavaScript centric (including JavaScript pushed from server): GWT, DWR.
Server centric: JSF, Wicket, Echo2, wingS, Tapestry, ItsNat
Custom tags based (HTML generated by the framework)/XML declarative programming (using expression languages etc): JSF, Struts (tons of similar frameworks), Tapestry.
View built programmatically: GWT, Echo2, wingS…
Pure HTML templates, components attached to the HTML using Java: Wicket, ItsNat.
Page centric: JSF, Struts, Wicket…
XML based navigation and bindings: JSF, Struts
Component based: all except Struts.
Focused to desktop-like web applications / initial page based on JavaScript (the browser receives the markup embedded in JavaScript (JS builds the page): IT Mill, GWT, DWR, Echo2, wingS, Eclipse RAP, Tapestry(?)
Not so focused to desktop-like app. (web site centric and search engines friendly) / initial page based on HTML (the browser receives serialized HTML): JSF, Struts, Wicket, ItsNat, Tapestry(?)
AJAX based components: JSF enriched, Wicket enriched, GWT, Echo2, wingS, DWR, ItsNat.
COMET/long polling built-in: IceFaces, ItsNat
Remote views of other users/pages: ItsNat
Server-sent events: ItsNat
Functional web testing built-in using the browser: ItsNat

Note: Tapestry is not clear because is integrated with Dojo, Dojo is for me in the "Initial page based on JavaScript" category.

For instance, if you don't like custom tags and view built programmatically, that is to say, you want pure HTML templates, you only have two options: Wicket and ItsNat, and if you are strongly focused on AJAX, you only have one option… ItsNat.

Disclaimer: I'm the author of ItsNat

Jose M. Arranz replied on Thu, 2008/02/07 - 9:03am