Cool Code
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Rob Thornton on Apr 12, 2007
Joe Walker has released the fourth release candidate of DWR 2.0. Significant changes include Guice support, security, and Reverse Ajax fixes.
DWR is a popular Ajax toolkit for Java. Version 2.0 has been in the works for quite awhile with Release Candidate 1 announced in early December of last year. The final release of 2.0 is expected in the next week. They found that Guice support was easy to add and did not affect the core code so they made the changes even though they are late in the release cycle. Tim created the Guice integration on his own and then connected with Joe to make it part of the DWR distribution.
Fortify performed an analysis of 12 different Ajax toolkits for how they stood up to JavaScript Hijacking techniques and while DWR stood up well, some weak points were noted and they have been shored up in this release.
Little remains to be done before a final release: a demo of TIBCO GI integration, a SingletonCreator, and a few bug fixes.
18 agile and lean practices for effective software development governance
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
No comments
Watch Thread Reply