@frameworks[:rails] << @frameworks[:merb] - Phoenix Ruby Users Group

Message from discussion @frameworks[:rails] << @frameworks[:merb]

David Koontz

More options Dec 25 2008, 2:27 am

From: David Koontz <dkoo...@gmail.com>

Date: Thu, 25 Dec 2008 00:27:03 -0700

Local: Thurs, Dec 25 2008 2:27 am

Subject: Re: [Phoenix Ruby Group] Re: @frameworks[:rails] << @frameworks[:merb]

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

I think this is fantastic. Why you say? Because Rails has mindshare
and you can get paid to write it. Merb is better implementation,
learning from all the mistakes of Rails and from its own first
versions. People I hear talking about learning Merb usually do so
because they're tired of Rails, but Rails is what you can get paid for
now. So soon, in Rails 3, you will get all the benefits of Rails
mindshare, etc., except that you'll be writing Merb code. It's like
if Sun and Matz got together and decided that Java 7 would be Ruby
1.9. Wow, we could all go out and get those great paying Java gigs.
Ok, perhaps a bit of a stretch but you get the idea.

The only fear I have is that Merb will be bogged down by the legacy
requirements of Rails. How many sacrifices will be made in the name
of backwards compatibility or supporting certain large user bases? If
it's a clean API break, then I salute the Rails team for having balls
of steel.

David Koontz

On Dec 24, 2008, at 12:43 PM, Chad Woolley wrote:

> On Tue, Dec 23, 2008 at 2:19 PM, Andy Ferra <afe...@gmail.com> wrote:
>> Yay!? Shit!? [50/50]

> Yay. I think the Merb guys will bring a lot of good to Rails,
> especially around disciplined APIs, and putting more heavy weight in
> one direction is good as well.

> Plus, Rails is on GitHub, as is Merb, so anyone who doesn't like it
> can fork and do their own thing. Competition and innovation will
> continue.

> -- Chad

Reply to author Forward