3 ms·
I disagree. It's pretty obvious that though a great number of changes came through with Rails 3, one of the goals was to have a short uptake path. This is readi
by jherdman 16y ago
I disagree. It's pretty obvious that though a great number of changes came through with Rails 3, one of the goals was to have a short uptake path. This is readily observed through the decision to maintain Prototype as the default JS library, ERB, and others, despite the gross popularity of the alternatives.
Introducing Arel, and improving ActiveRecord in general, serve to bolster this attitude and approach. That is, to improve the state of the defaults, provide an easy path for uptake, whilst now offering the alternatives cleaner means of tying into the Rails system.
To address your side nodes...
#1. A hat tip would have been nice, but I don't think too many folks were truly upset in the long run.
#2. Meh. The only thing I really miss from DM is the declaration of attributes. Arel is pretty tight. Check out Mongoid. It's pretty slick.
#3. Ex-Merb user too. AR does the trick sometimes, but I'm happy to have the freedom to use Mongoid, Sequel, etc.
- technoweenie 16y ago1. I think it goes to show how well the Rails and Merb teams were able to integrate. Things were a bit rocky in the early days of the merger though :) A big merger like that could easily have self destructed. 2. You should be able to do that in AR by adding to the class-level #columns collection yourself. I had a plugin for this years ago for validating contact models. I'd imagine it's even easier in 3.0 since ActiveModel requires attributes to be set. 3. I really like the work that Josh and the rest put into ActiveModel. It happened to materialize around the time various alternate datastores like Mongo started getting popular.