Hi Andrey, On 22/07/2010 18:03, AndreyRybin wrote: > > I am happy Click user. > But my manager has too much free time ;-) > > So I need help. > He read many articles about http://www.playframework.org/ and > http://www.grails.org (nothing dangerous yet, but bad sign).
I don't have experience with either of these frameworks so cannot really comment. However its always good to look at different technologies and what they offer. > They both have some cool features, but I think they are step back after > component frameworks. I agree. However I don't mind simple action based web frameworks though. They are easy learn and use, have great performance but don't lend themselves to create reusable functionality. Off course one can create custom tag libraries, but that is quite low level plumbing and are usually difficult to debug. On the other end of the spectrum there are stateful component based web frameworks. They provide reusable components but are generally quite sophisticated. My biggest gripe with stateful frameworks is they are built on the premise that the web will be a better place if it was more like the desktop. I never understood this approach because the web had a great affect on user interfaces. If anything, desktop applications will be better if it took some lessons from the web. Make UIs easy, simple and intuitive. Generally it takes a lot of effort to make a desktop application that is user friendly. The web on the other hand has simplicity and ease of use built into it. In fact it is very hard to make a complex application on the web and that is a good thing, especially for your users. Anyway here is my 'tongue-in-cheek' attempt at Click hype: Overview: Click is a unique web framework in the Java landscape. It took the best of both stateless (action based) and stateful (component based) frameworks and combined it to provide a unique blend of simplicity, easy of use, productivity and performance. Click is stateless but also provides a higher level of abstraction through Pages and Controls. Developers have full access to the Servlet API and can leverage Velocity for custom rendering and layout if a Control default is not satisfactory. Simplicity: The core framework consists of 80 classes, half of which are components. There are no complicated abstractions to study and learn. With a basic understanding of Servlets and HTML you should be up and running within a day. Getting up to speed quickly is important in enterprise environments with high staff turnover. Easy of use: There is the ClickServlet, the Page and the Control. That's pretty much it. Majority of coding is done in Java. When stuck, use your IDE debugger to step through the code. For full transparency, Click source code is shipped with the jar, making it easy to step into and see what is happening behind the scenes. If that wasn't enough Click has some of the best documentation and examples available. It's Javadoc is probably the best in the business. Performance: Click's performance is legendary. Click, a component based framework, handles more requests per second than any of the request based frameworks we've tested against. And it's not even fully optimized yet. No need to even compare Click's performance against stateful frameworks, they didn't even leave the starting blocks by the time Click lapped them... for the third time. OK, that was fun but not really all that serious :) Kind regards Bob PS: Don't believe framework hype. Take frameworks for a spin, if it suits you, use it, if not, dump it. PSS: http://en.wikipedia.org/wiki/No_Silver_Bullet
