News for hackers. Stuff that matters.
Re:Moving to Rails 2.2 Headaches - Vol 1 by river_styx on Monday November 24, 2008 @08:40PM (#375824)
The has_many_polymorphs plugin is also broken in 2.2 as of right now.
Re:Moving to Rails 2.2 Headaches - Vol 1 by mattjaynes on Monday November 24, 2008 @06:44PM (#375665)
Exactly why the future's so bright for merb...
Re:Moving to Rails 2.2 Headaches - Vol 1 by tptacek on Monday November 24, 2008 @06:54PM (#375687)
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?
Re:Moving to Rails 2.2 Headaches - Vol 1 by mattjaynes on Monday November 24, 2008 @07:03PM (#375699)
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/

Re:Moving to Rails 2.2 Headaches - Vol 1 by wmoxam on Monday November 24, 2008 @11:32PM (#375988)
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.

Re:Moving to Rails 2.2 Headaches - Vol 1 by jcapote on Tuesday November 25, 2008 @12:00AM (#376020)
Holy plugins batman!
Re:Moving to Rails 2.2 Headaches - Vol 1 by dexter on Monday November 24, 2008 @08:31PM (#375807)
Yeah we're using mercurial, what of it? Did I mention we use mercurial?