Comments on: Will Rails go the Struts 1 way ? http://blog.dhananjaynene.com/2008/12/will-rails-go-the-struts-1-way/ Dhananjay Nene's opinions on software programming, design, architecture and the internet Sun, 28 Feb 2010 03:58:25 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: dipankarsarkar http://blog.dhananjaynene.com/2008/12/will-rails-go-the-struts-1-way/comment-page-1/#comment-3046 dipankarsarkar Mon, 29 Dec 2008 18:54:10 +0000 http://blog.dhananjaynene.com/?p=312#comment-3046 I would think that rails would dominate in the merging ... though there are some positives to be taken from the merb codebase .... I would think that rails would dominate in the merging … though there are some positives to be taken from the merb codebase ….

]]> By: lowell http://blog.dhananjaynene.com/2008/12/will-rails-go-the-struts-1-way/comment-page-1/#comment-2599 lowell Fri, 26 Dec 2008 05:05:20 +0000 http://blog.dhananjaynene.com/?p=312#comment-2599 "I really cannot imagine easily merging two frameworks and have the best of both of them be reflected in the result "<br><br>Merb, to put it as simply as possible, is a pluggable, unopinionated, not-as-mature, but definitely usable version of Rails.<br><br>It isn't a merger of equals, Merb is being consolidated into Rails 3. I'm expecting Rails to support ORMs other than AR out of the box and to also support templating languages other than ERb out of the box (hopefully adding Haml). They're going to add a consistent API plugins and crap don't outdated with every point release.<br><br>Basically, it's going to have Rails try to cater to everything, which goes against the DHH's original vision. It's annoying, but there's no way I'm going to stop coding in Ruby - I've gotten too used to it. Besides, the move was to unify the existing Ruby community and to not confuse newcomers.<br><br>So, um. Yeah. What I was going to say before I got sidetracked is that no, merging them is not going to be as difficult as you might think as the two have much in common as it is (workflow-wise, not code-wise). “I really cannot imagine easily merging two frameworks and have the best of both of them be reflected in the result “

Merb, to put it as simply as possible, is a pluggable, unopinionated, not-as-mature, but definitely usable version of Rails.

It isn't a merger of equals, Merb is being consolidated into Rails 3. I'm expecting Rails to support ORMs other than AR out of the box and to also support templating languages other than ERb out of the box (hopefully adding Haml). They're going to add a consistent API plugins and crap don't outdated with every point release.

Basically, it's going to have Rails try to cater to everything, which goes against the DHH's original vision. It's annoying, but there's no way I'm going to stop coding in Ruby – I've gotten too used to it. Besides, the move was to unify the existing Ruby community and to not confuse newcomers.

So, um. Yeah. What I was going to say before I got sidetracked is that no, merging them is not going to be as difficult as you might think as the two have much in common as it is (workflow-wise, not code-wise).

]]> By: Caligula http://blog.dhananjaynene.com/2008/12/will-rails-go-the-struts-1-way/comment-page-1/#comment-2538 Caligula Wed, 24 Dec 2008 22:17:48 +0000 http://blog.dhananjaynene.com/?p=312#comment-2538 There are more similarities between Rails/Merb than S1 and WW/S2. There are more similarities between Rails/Merb than S1 and WW/S2.

]]>