Agile in Practice: What Is Actually Going On Out There?
Scott Ambler talks about actual data resulting from surveys made during 2006-2008, showing how Agile is perceived and implemented within organizations.
Tracking change and innovation in the enterprise software development community
Posted by Rob Thornton on Jan 12, 2007 08:00 AM
ONJava has a review of Wicket. He concludes that Wicket is a good contender if you're looking for a component-oriented web application framework.
Timothy O'Brien has written about selecting a web application framework and continues to review different tools. His first impression of Wicket is:
It's different, in some ways refreshing, but like all web frameworks, it comes with a special set of problems. It's a little code heavy to be considered cool by the Web 2.0 crowd. But, at the risk of sounding like a Java developer, there's nothing wrong with writing compiled code now and then, and Wicket seems to make it easy to approach web application design from an OO "mindset".
After the common reaction of "do we need another framework", he goes through two different opinions. The first:
Wicket is an awful code explosion, written by Java-intoxicated programmers. ...In this age of lightness, Wicket is a heavy hammer. If you are looking for Hello World in 1 minute, run toward something else as quickly as you can.
After that strong negative reaction, O'Brien comes around to a even stronger positive reaction. He notes that it is a valid criticism to call it code heavy but maintains that not having to deal with markup more than makes up for it.
if you are looking for the Hello World in One Minute framework, there's a good chance that you are not developing a real application. Wicket brings complexity in the form of a rich component framework, but this complexity brings with it the ability to code a web site without having to code yet another table, or yet another paging mechanism. Believe it or not, the code you end up creating with Wicket is clean, and from what I've seen you don't end up making any compromises wrt to separation of presentation and logic.
InfoQ has covered Wicket in the past, when version 1.2 was released and a comparison with JSF and Spring MVC
The End of Middleware: Freedom from IT Stacks as we know it
Spring App Platform, Java Concurrency/Multicore, Eclipse Mylyn and more @ QCon SF Nov 19-21
Guide to Calculating ROI with Terracotta Open Source JVM Clustering
I think there probably should have been a link to the article mentioned http://www.oreillynet.com/onjava/blog/2007/01/wicket_another_java_web_framew.html The one included seems to have been written 6 months ago.
Wicket is an awful code explosion, written by Java-intoxicated programmers. ...In this age of lightness, Wicket is a heavy hammer. If you are looking for Hello World in 1 minute, run toward something else as quickly as you can.
public class HelloWorld extends wicket.markup.html.WebPage {
public HelloWorld(){
add(new wicket.markup.html.basic.Label("helloLabel", "Hello World"));
}
}
where HelloWorld.html BODY tag contains :
Hello World ! placeholder
Wicket may be a heavy hammer but for complex things you may need a heavy hammer. But Hello World seekers should NOT run anywhere because the above snippets look FAR MORE BETTER than the most java web development frameworks I've seen.
As for the "java intoxicated programmers" (first, isn't that classification a little bit awkward comming from a site called onjava.com ? :-)) ), if that means developing with Wicket requires java and nothing else, than why not ? :-D ?
Scott Ambler talks about actual data resulting from surveys made during 2006-2008, showing how Agile is perceived and implemented within organizations.
From QCon 2008, Daniel Moth presents on using Visual Studio 2008 and .NET 3.5 to create compelling rich Windows applications.
Joshua Kerievsky, founder of Industrial Logic, talks about Industrial Extreme Programming which extends XP by including practices dealing with management, customers and developers.
Amazon Web Services (AWS) Evangelist Jeff Barr discusses SimpleDB, S3, EC2, SQS, cloud computing, how different Amazon services interact, origins of AWS, AWS globalization and the March AWS outage.
Cloud services have helped bring virtualization to the forefront. Its full power however, also includes other benefits such as high availability, disaster recovery, and rapid provisioning.
John Lam talks about his path to dynamic languages, some of the problems of making IronRuby run fast, and how the DLR helps with implementing languages.
VMware Infrastructure 3: Advanced Technical Design Guide and Advanced Operations Guide provides a wealth of practical insights into setting up virtualization in todays corporate environments.
Can a system that is so large it cannot be comprehended be "designed" in a conventional sense? The foundations of computing are about to change. In this talk, Richard P. Gabriel explores why and how.
2 comments
Reply