Moving to Rails 2.2 Headaches - Vol 1(gusg.us)
gusg.us
Moving to Rails 2.2 Headaches - Vol 1
http://gusg.us/code/ruby/rails-2_2-headaches-1
8 comments
The has_many_polymorphs plugin is also broken in 2.2 as of right now.
Exactly why the future's so bright for merb...
Because an application with a complicated set of external dependencies was ported warning-free to the newest version of Rails in a matter of hours, within days of the new version's release?
Yes.
"Merb has an API. You might be wondering why having an API is awesome. Well, the truth is that the Merb Team spent time marking methods public, which are guaranteed to not break until the next major release (any change to the public API will be well documented). There is also a plugin API meaning that plugin developers won’t have to worry about upgrades if they stick to the plugin API."
From: http://merbist.com/2008/11/09/merb-1-0-released/
"Merb has an API. You might be wondering why having an API is awesome. Well, the truth is that the Merb Team spent time marking methods public, which are guaranteed to not break until the next major release (any change to the public API will be well documented). There is also a plugin API meaning that plugin developers won’t have to worry about upgrades if they stick to the plugin API."
From: http://merbist.com/2008/11/09/merb-1-0-released/
It'll be interesting to see how well it works in the coming releases of Merb.
I'm not being a hater, just saying it hasn't been tested. Hopefully they can pull off upgrades more smoothly than Rails and Rails can learn from it. That way everyone wins.
I'm not being a hater, just saying it hasn't been tested. Hopefully they can pull off upgrades more smoothly than Rails and Rails can learn from it. That way everyone wins.
Holy plugins batman!
Yeah we're using mercurial, what of it? Did I mention we use mercurial?