Comments on: Rails and Merb Merge: The Anniversary (Part 1 of 6) http://www.engineyard.com/blog/2009/rails-and-merb-merge-the-anniversary-part-1-of-6/ Wed, 08 Feb 2012 12:12:12 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Eduardo http://www.engineyard.com/blog/2009/rails-and-merb-merge-the-anniversary-part-1-of-6/comment-page-1/#comment-43765 Eduardo Sun, 22 Aug 2010 21:18:04 +0000 http://www.engineyard.com/blog/?p=3062#comment-43765 Matt Aimonetti a merb's core team member answered to the question "I just started a merb project, so what now?" "Keep on using Merb, we won’t let you down." ~ Matt Aimonetti The interview is here <a href="http://merbist.com/2008/12/23/rails-and-merb-merge/" target="_blank">http://merbist.com/2008/12/23/rails-and-merb-merg...</a> -- Do not promise what you can't accomplish Matt Aimonetti a merb's core team member answered to the question "I just started a merb project, so what now?"

"Keep on using Merb, we won’t let you down." ~ Matt Aimonetti

The interview is here http://merbist.com/2008/12/23/rails-and-merb-merg… — Do not promise what you can't accomplish

]]> By: k776 http://www.engineyard.com/blog/2009/rails-and-merb-merge-the-anniversary-part-1-of-6/comment-page-1/#comment-38682 k776 Wed, 30 Dec 2009 05:01:01 +0000 http://www.engineyard.com/blog/?p=3062#comment-38682 Merb is open source. If development has stalled, it was abandoned by the entire community, and not just the people who were working on it. Merb is open source. If development has stalled, it was abandoned by the entire community, and not just the people who were working on it.

]]> By: Carlton http://www.engineyard.com/blog/2009/rails-and-merb-merge-the-anniversary-part-1-of-6/comment-page-1/#comment-38660 Carlton Tue, 29 Dec 2009 21:14:15 +0000 http://www.engineyard.com/blog/?p=3062#comment-38660 I want to use it not get hyped about it. I want to use it not get hyped about it.

]]> By: Sindre http://www.engineyard.com/blog/2009/rails-and-merb-merge-the-anniversary-part-1-of-6/comment-page-1/#comment-38602 Sindre Fri, 25 Dec 2009 14:00:00 +0000 http://www.engineyard.com/blog/?p=3062#comment-38602 It is a disgrace to see how Merb was completely and utterly abandoned by the whole core-team after they we're invited to work on rails. Lots of people who were using Merb in large production deployments got screwed pretty badly. If Rails is a ghetto, then I cannot begin to describe what the Merb -> Rails merger made Merb become. On a positive note, it made me see why people actually use Java and it's heavyweight frameworks for large projects. If something can go from having a large and vibrant community one day, to months without simple bugfixes and pure silence, then it is smart to stay far away from it for anything serious. But yes, Rails 3 seems promising, and you have madesome awesome improvements. I think I will stick to Sinatra myself. I just hope no one tries to lure its core devs over to something else with promises of fame and glory. It is amazing to see how much can be done using Sinatra, with it's tiny and understandable codebase. It is a disgrace to see how Merb was completely and utterly abandoned by the whole core-team after they we're invited to work on rails. Lots of people who were using Merb in large production deployments got screwed pretty badly. If Rails is a ghetto, then I cannot begin to describe what the Merb -> Rails merger made Merb become. On a positive note, it made me see why people actually use Java and it's heavyweight frameworks for large projects. If something can go from having a large and vibrant community one day, to months without simple bugfixes and pure silence, then it is smart to stay far away from it for anything serious.

But yes, Rails 3 seems promising, and you have madesome awesome improvements. I think I will stick to Sinatra myself. I just hope no one tries to lure its core devs over to something else with promises of fame and glory. It is amazing to see how much can be done using Sinatra, with it's tiny and understandable codebase.

]]> By: cies http://www.engineyard.com/blog/2009/rails-and-merb-merge-the-anniversary-part-1-of-6/comment-page-1/#comment-38598 cies Fri, 25 Dec 2009 10:43:20 +0000 http://www.engineyard.com/blog/?p=3062#comment-38598 What's in the name Action/Active? Sound like ActiveDirectory and ActiveSync.. Strange branding in my eyes: the name is Rails, right? What about RailsController, RailsSupport, or Rails::Controller, Rails::Support? It simply makes more sense to me. Rubyists care for meaningful naming right? I'm a merb lover: for its simplicity. Reading this write-up I think R3 is on its way to replace merb for me. The weird action/active naming will not hold me down. :) Thanks for the write up! What's in the name Action/Active? Sound like ActiveDirectory and ActiveSync.. Strange branding in my eyes: the name is Rails, right? What about RailsController, RailsSupport, or Rails::Controller, Rails::Support? It simply makes more sense to me. Rubyists care for meaningful naming right?

I'm a merb lover: for its simplicity. Reading this write-up I think R3 is on its way to replace merb for me. The weird action/active naming will not hold me down. :)

Thanks for the write up!

]]> By: Paul http://www.engineyard.com/blog/2009/rails-and-merb-merge-the-anniversary-part-1-of-6/comment-page-1/#comment-38581 Paul Thu, 24 Dec 2009 21:26:26 +0000 http://www.engineyard.com/blog/?p=3062#comment-38581 These implicit requirements are a huge headache with maintaining Ruby code. I prefer other languages that require each file to list its dependencies. These implicit requirements are a huge headache with maintaining Ruby code. I prefer other languages that require each file to list its dependencies.

]]> By: wycats http://www.engineyard.com/blog/2009/rails-and-merb-merge-the-anniversary-part-1-of-6/comment-page-1/#comment-38580 wycats Thu, 24 Dec 2009 17:30:27 +0000 http://www.engineyard.com/blog/?p=3062#comment-38580 Plugins should individually pull in the parts of ActiveSupport that *they* need. You'll only need to pull in parts of ActiveSupport that you're explicitly using -- I agree that otherwise the idea would be untenable. Plugins should individually pull in the parts of ActiveSupport that *they* need. You'll only need to pull in parts of ActiveSupport that you're explicitly using — I agree that otherwise the idea would be untenable.

]]> By: Guoliang Cao http://www.engineyard.com/blog/2009/rails-and-merb-merge-the-anniversary-part-1-of-6/comment-page-1/#comment-38578 Guoliang Cao Thu, 24 Dec 2009 16:29:31 +0000 http://www.engineyard.com/blog/?p=3062#comment-38578 Thanks a lot for the write up. Regarding "You’ll still need to include the fancy parts if you want to use them – 3.days wont work out of the box with bare enabled", for a sizable project that uses plugins, it is hard to imagine to enable bare mode. Thanks a lot for the write up.

Regarding "You’ll still need to include the fancy parts if you want to use them – 3.days wont work out of the box with bare enabled", for a sizable project that uses plugins, it is hard to imagine to enable bare mode.

]]> By: Georg Kreimer http://www.engineyard.com/blog/2009/rails-and-merb-merge-the-anniversary-part-1-of-6/comment-page-1/#comment-38576 Georg Kreimer Thu, 24 Dec 2009 15:04:49 +0000 http://www.engineyard.com/blog/?p=3062#comment-38576 Good stuff as usual wycats. Looking forward to use Rails 3 very soon. Good stuff as usual wycats. Looking forward to use Rails 3 very soon.

]]> By: hipertracker http://www.engineyard.com/blog/2009/rails-and-merb-merge-the-anniversary-part-1-of-6/comment-page-1/#comment-38570 hipertracker Thu, 24 Dec 2009 10:30:20 +0000 http://www.engineyard.com/blog/?p=3062#comment-38570 ..in next year I am afraid.... Is there any timeline for Rails 3??? ..in next year I am afraid…. Is there any timeline for Rails 3???

]]>