All geek questions in one place

What can I expect as the main stack for Rails 3.0 and what I now need to include as a plugin

So, is Rails and Merb a merger in Rails 3.0? The way it was described to me in any case. This means that much of what Rails has done, Rails has now been ported to plugins to make it easier. In any case, what will these plugins be and how will the new Rails developer look, what should be - and even more mature - the plugins that the Rails developer should install? Some good examples I can think of might be will_paginate, ruby_prof, or sqlite3-ruby.

+3
source share
2 answers

I understand that Rails (3) will continue to consist of the infrastructure components that make up it now, i.e. ActiveRecord, ActiveSupport, ActionPack, even prototype.js, etc. It's just that the inside has been significantly reorganized and cleaned up and it will be much easier to swap components for alternatives. For example, perhaps replacing ActiveRecord with a Data Mapper.

  • The tag line for Rails 3 is the same as Burger King ie Have It Your Way (I'm not joking!)
+4
source

Many releases extracted significant components and put them into plugins; you probably didn’t even notice most of the time. It would be best to just stay up to date and pay attention to the deprecation messages in your logs, and everything will be fine.

, . , .

+1

Source: https://habr.com/ru/post/1727501/

More articles:


All Articles