&#62; I don't believe the new Web 2.0 frameworks are the answer<p>I strongly disagree, there are a growing number of people that are discovering that abandoning the server for UI, liberates them from this atrocious development methodology that web developers have been locked in.<p>Using a prototype based scripting language (Javascript) for the UI and coupling that to strongly defended (security, type safety, validation) REST services gives you a rapid UI for users to touch feel and change while Strongly typed services give you the metrics that the IT department needs to insure they are not getting crap in their system.<p>This is why products like flash made huge inroads over swing and other UI development products because they offered the people that use them the speed and flexibility they need.<p>Java on the other-hand has been the enterprise standard for as long as COBOL has not. Because it is safe and rigid and has a huge library, all the things a UI designer does not need.<p>For two long we have made one party or the other suffer the sins of the other development methodologies practice. Even if you are a long gunman (I now am). It is still a far more productive way to develop web applications.<p>The client model become very clear when one abandon the server model. The funny part is it makes both sides so drop dead simple that anything beyond the toolkits seem like overkill. The frameworks are so light they almost seem non-existent. It is very natural once one liberates oneself of the years of indoctrination of doing it the old way and stop trying to just sprinkle some in.