4 ms·
I remember a blog post from 2008: Rails will be retrofitted to make it easy to start with a “core” version of Rails (like Merb’s current core generator), that
by MartinMond 15y ago
I remember a blog post from 2008:
Rails will be retrofitted to make it easy to start with a “core” version of Rails (like Merb’s current core generator), that starts with all modules out, and makes it easy to select just the parts that are important for your app. Of course, Rails will still ship with the “stack” version as the default (just as Merb does since 1.0), but the goal is to make it easy to do with Rails what people do with Merb today.
http://yehudakatz.com/2008/12/23/rails-and-merb-merge/ http://yehudakatz.com/2008/12/23/rails-and-merb-merge/
- epochwolf 15y agoAnd they have been moving in this direction. Here's configuring the middleware: http://guides.rubyonrails.org/rails_on_rack.html http://guides.rubyonrails.org/rails_on_rack.html Here's a stackoverflow question on how to disable ActiveRecord: http://stackoverflow.com/questions/2212709/remove-activerecord-in-rails-3-beta http://stackoverflow.com/questions/2212709/remove-activereco... Have you seen ActiveModel? It gives a common interface for orms to interface with so swapping out ActiveRecord doesn't break half of the view helpers. Rails 3 is far, far easier to extend and modify than 2.3 was.