Exploring Active Record

Created By: ahammock
Last Modified: 06/09/06
Ruby on Rails seems to be a lightning rod for controversy. At the heart
of most of the controversy lies amazing productivity claims. Crossing Borders
author Bruce Tate has come to understand that Rails isn't a better
hammer; it's a different kind of tool. This article explores the
compromises and design decisions that went into making Rails so
productive within its niche. Then it looks at Rails-inspired ideas that
should get more attention within the Java™ community.
From: http://www-128.ibm.com/developerworks/web/library/j-cb05096.html?ca=dgr-lnxw01RailsSecretSauce
The Java™ programming language has had an unprecedented run of
success for vendors, customers, and the industry at large. But no
programming language is a perfect fit for every job. This article
launches a new series by Bruce Tate that looks at ways other languages
solve major problems and what those solutions mean to Java developers.
He first explores Active Record, the persistence engine behind Ruby on
Rails. Active Record bucks many Java conventions, from the typical
configuration mechanisms to fundamental architectural choices. The
result is a framework that embraces radical compromises and fosters
radical productivity.
From: http://66.94.229.32/myresults/mycache?u=http%3A%2F%2Fwww-128.ibm.com%2Fdeveloperworks%2Fjava%2Flibrary%2Fj-cb03076&docid=J0aQ8tBQlyJw5WHWHbwrug&.intl=us&.done=http%3A%2F%2Fmyweb2.search.yahoo.com%2Fmyweb%3F%253Ffr%3Dmy-vert-web-top%26ei%3DUTF-8

