Agreed, but let's keep in mind that things happened that allowed us to let go of many of the frameworks many of us were initially drawn to. Firstly, there was the move to stronger standardization of things like DOM, CSS, and HTML and better implementations in the browsers, particularly the welcome demise of IE6. On the other hand, much more work was put into client-side frameworks/libraries like jQuery and YUI. And of course we're now also seeing the rise of frameworks like GWT that give us client-side language of our choice (Java) with all the usual perks (strong typing, back-end interoperability, seamless RPC).
The end result of all this is that there are more than ever reasons to reduce complexity on the back end and leverage client-side standards and libraries with significant momentum behind them. I think the debates died down largely because of these changes in our web-dev ecosystem than due to any side winning over the philosophical framework arguments that once seemed so far-reaching. On Oct 28, 12:39 pm, clay <[email protected]> wrote: > Five years ago, there were intense debates of web frameworks. There > were Java framework wars among Struts vs JSF vs Tapestry vs Wicket vs > Spring vs etc along with the the prominent non-Java frameworks such as > PHP, ASP.NET, Rails, etc. > > Recently, I've been working on rich web applications that use: > - 100% static HTML/JavaScript/CSS > - Client-side JavaScript GUI framework such as ExtJS or YUI or > something similar. > - Server-side web services such as JAX-RS/JSON or something similar. > > No traditional server-side HTML web framework. > > This really seems like the perfect dev stack for the web. The tools > are extremely easy to learn and use and debug. I can edit static HTML/ > JS content and get feedback instantly or edit server-side code and > restart web services in seconds. There is no code generation, which > from past experience always leads to headaches eventually. Completely > separate client/server source code is much easier to read, edit, and > works much better with syntax highlighting than hybrid server-side > template files that mixed template markup, server code, and client > code. And, most importantly, the end web apps are extremely high > quality, extremely fast, and fully customizable. > > Having done hundreds of web projects with dozens of web frameworks, > and witnessing so much debate about which framework was better, I'm > amazed at how much better web development is without any traditional > framework piece at all. > > So, would people tend to agree? I'm also surprised that after how > heated the server-side web framework wars got, few people have > mentioned their obsolescence. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
