Live data from Hacker News

Rails and Merb Merge

yehudakatz.com

51–57 of 57 posts

Re: Rails and Merb Merge

#51

Do I detect the hand of Benchmark Capital here? Edit: I wrote the orginal comment in a hurry - but what I was getting at was that Engine Yard took quite a bit of cash from Benchmark. I somehow doubt that a move like this could have happened without their approval, and I have to wonder if they instigated it (and why...)

[deleted]

Re: Rails and Merb Merge

#52
post #3

Wow, big news. I'm mixed on this. One of the strengths of Rails was that it was the dominant Ruby web programming framework. This meant that virtually the entire community was behind Rails when it came to web app development - unlike some other languages, which have several frameworks competing for the crown. But Merb has recently started to give Rails a run for its money. Fortunately, the learning curve between Merb…

That's alright, we have Sinatra for innovation now: http://sinatra.rubyforge.org/

Re: Rails and Merb Merge

#54
post #4

Impressive! How often do you hear about two open-source projects merging? Forking is much more common. I can't even recollect other instances of merging. Best of luck to the two teams with making it work!

WebWork and Struts merged to become Struts 2...

This is the best comparison. Struts was great when it came out and inspired a lot of 2nd gen frameworks like Webwork. Webwork was very clever and much improved over struts. However, struts was far more popular. Bringing the two together created a better product that was adopted by the mainstream java web developers. It was a great way to get the developers that were stuck on struts (for whatever reason, most likely to support existing code bases) into a better design.

In about a year I could write the paragraph above substituting rails for struts, merb for webwork, and java for ruby.

Re: Rails and Merb Merge

#55
post #9

Wow, I almost wish it were April Fools Day... For someone who loves Merb and had decided to leave Rails behind (as much as possible), I have very mixed feelings about this. If this means Rails will start to feel more like Merb, fantastic! Otherwise? I have a feeling it'll be a long while before I really know how to feel about this... It'll be interesting to see how well this merger actually works in practice. It seem…

Yes, it means Rails will feel more like Merb. From the article:

"As you have probably gathered from the above, there aren’t any clear points that the Merb and Rails team disagree on anymore."

Basically, Rails is being reworked to be more modular, to have less tight coupling among components, to have a defined API and test suite, to support other ORMs, etc. These are the reasons Merb came to be, and the merge back into Rails vindicates the Merb team's design decisions.

Re: Rails and Merb Merge

#56
post #47

this is huge. and it turns out that yesterday i was considering learning merb instead of rails. but for the moment i will learn rails. what is the best one to learn at the moment in order to be ready for rails 3?

Both. They're both Ruby. The learning curve for one over the other changes very little ultimately. In practice, however, Merb docs, tutorials, articles, howtos, et cetera, are lacking. That is reality. If you're starting from scratch w/ Ruby and her frameworks, you'll probably find Rails more newbie-friendly from a learning-materials standpoint.

Interesting, Thanks!
Post reply on HN