Why GWT? Part II: The right tools for the job
Last time I talked about moving beyond the page metaphor to create truly dynamic and interactive web applications. Today I’ll talk about why I think GWT is a good means to this end.
When I talk to people about Accevia or my other projects, they often ask why I decided to use GWT instead of common frameworks like Django or Ruby on Rails. I’m a big fan of both, but I don’t actually see them as direct competitors to GWT. Both are designed around the page metaphor and are excellent tools for creating sites that can be structured in this way. But they just aren’t the right tool for dynamic web applications. Let’s take a look at why this is.
Imagine creating an application like Google Calendar in Rails. Rails makes heavy use of the Model-View-Controller pattern, so we need to break our application into different views. Obviously we can make a view for the main calendar page, and probably a separate view for creating a new event. Maybe we can make one for the settings page also. These three views cover pretty much everything, now it’s just a matter of implementing them.