Comments on: Magnificent Merb (and Sequel?) http://blog.inquirylabs.com/2007/08/02/magnificent-merb-and-sequel/ Politics, Programming and Possibilities Thu, 11 Mar 2010 23:52:54 +0000 http://wordpress.org/?v=2.6.1 By: Ari http://blog.inquirylabs.com/2007/08/02/magnificent-merb-and-sequel/#comment-14341 Ari Fri, 10 Aug 2007 06:04:49 +0000 http://blog.inquirylabs.com/2007/08/02/magnificent-merb-and-sequel/#comment-14341 Ever wanted rSpec to work with merb? Took a while, but now you can! <a href="http://blog.xnot.org/2007/08/09/rspec-on-merb/" rel="nofollow">http://blog.xnot.org/2007/08/09/rspec-on-merb/</a> Let me know how it works for you Ever wanted rSpec to work with merb? Took a while, but now you can!

http://blog.xnot.org/2007/08/09/rspec-on-merb/

Let me know how it works for you

]]> By: Ezra http://blog.inquirylabs.com/2007/08/02/magnificent-merb-and-sequel/#comment-14095 Ezra Sun, 05 Aug 2007 20:44:16 +0000 http://blog.inquirylabs.com/2007/08/02/magnificent-merb-and-sequel/#comment-14095 Originally I was working on improving rails itself instead of making a new framework. The problem is that Rails is just to big at this point and has too much backwards compatibility baggage to make radical changes to the code. It has matured to the point where radical changes are very hard to accomplish without pissing people off by breaking some feature they were using. We all love rails, myself included. But there are some things I don't agree with in the rails code base. People say constraints are liberating but I think constraints are also constraining ;) Merb is going to be a lightweight hackers framework. Small core that is easy to extend, everything else is a plugin. I don't need the kitchen sink. Now if the rails core team wanted to release the current edge rails as rails 1.5 or something and would allow for some serious refactoring and BC breakage for rails 2.0 then I would gladly apply all of merb to rails 2.0 and kill the merb project. But I serioulsy doubt that is going to happen. Rails code base has gotten huge and complicated with tons of uneeded cleverness just for cleverness sake. I'd love to see Rails2.0 really thin down the core framework and rewrite all of ActionPack/ActionView. Originally I was working on improving rails itself instead of making a new framework. The problem is that Rails is just to big at this point and has too much backwards compatibility baggage to make radical changes to the code. It has matured to the point where radical changes are very hard to accomplish without pissing people off by breaking some feature they were using.

We all love rails, myself included. But there are some things I don’t agree with in the rails code base. People say constraints are liberating but I think constraints are also constraining ;) Merb is going to be a lightweight hackers framework. Small core that is easy to extend, everything else is a plugin. I don’t need the kitchen sink.

Now if the rails core team wanted to release the current edge rails as rails 1.5 or something and would allow for some serious refactoring and BC breakage for rails 2.0 then I would gladly apply all of merb to rails 2.0 and kill the merb project.

But I serioulsy doubt that is going to happen. Rails code base has gotten huge and complicated with tons of uneeded cleverness just for cleverness sake. I’d love to see Rails2.0 really thin down the core framework and rewrite all of ActionPack/ActionView.

]]> By: AkitaOnRails http://blog.inquirylabs.com/2007/08/02/magnificent-merb-and-sequel/#comment-13938 AkitaOnRails Fri, 03 Aug 2007 15:13:34 +0000 http://blog.inquirylabs.com/2007/08/02/magnificent-merb-and-sequel/#comment-13938 I like Merb too, I think that Ezra is one of the pinacles on Ruby performance. I am all for a good high-performance, concurrent web framework, but instead of building new alternatives from scratch I always wonder if it is not possible to tweak Rails itself, optimize it. Building something new always means another learning curve, redundant code and libraries. Rails already have the market share, the community attention, lots of documentation and support. Even though I like the ideas behind Merb I think it could do much better to add these to Rails. For example, ActiveRecord was not thread-safe, but after some tweaking from the Core Team and the community they were able to make it thread-safe. Well, just my 2 cents. I like Merb too, I think that Ezra is one of the pinacles on Ruby performance. I am all for a good high-performance, concurrent web framework, but instead of building new alternatives from scratch I always wonder if it is not possible to tweak Rails itself, optimize it. Building something new always means another learning curve, redundant code and libraries. Rails already have the market share, the community attention, lots of documentation and support. Even though I like the ideas behind Merb I think it could do much better to add these to Rails. For example, ActiveRecord was not thread-safe, but after some tweaking from the Core Team and the community they were able to make it thread-safe. Well, just my 2 cents.

]]>