Comments on: Is the Rails process too slow? http://casperfabricius.com/site/2007/11/25/rails-process-slow/ expert ruby on rails development Thu, 20 Nov 2008 22:22:01 +0000 http://wordpress.org/?v=2.6.2 By: Jakob S http://casperfabricius.com/site/2007/11/25/rails-process-slow/#comment-138 Jakob S Mon, 26 Nov 2007 13:17:36 +0000 http://casperfabricius.com/blog/2007/11/25/rails-process-slow/#comment-138 It would be interesting if you could run the numbers for Rails again once Report 12 have been in place for some while. Report 12 in itself is a sign that the lengthy process have been recognized by the Core team and they're attempting to address it. Running the numbers again could indicate wether Report 12 is successful. It would be interesting if you could run the numbers for Rails again once Report 12 have been in place for some while.

Report 12 in itself is a sign that the lengthy process have been recognized by the Core team and they’re attempting to address it. Running the numbers again could indicate wether Report 12 is successful.

]]> By: Andrew Bennett http://casperfabricius.com/site/2007/11/25/rails-process-slow/#comment-137 Andrew Bennett Mon, 26 Nov 2007 01:26:49 +0000 http://casperfabricius.com/blog/2007/11/25/rails-process-slow/#comment-137 I think the slow development process is due in part to the large number of people submitting poorly written patches or no patch at all, leaving the Rails community to figure out the problem for them. Using their new procedure for submitting patches might help to speed things up. <a href="http://dev.rubyonrails.org/ticket/9890" title="Rails ticket #9890" rel="nofollow">One of my patches</a> was <a href="http://dev.rubyonrails.org/changeset/7945" rel="nofollow">accepted</a> just 2 hours after I submitted it. I think they could also significantly speed things up if they'd migrate to a distributed version control system (whether it's git, mercurial, bzr, etc). Almost <em>anything</em> is better than subversion. I think the slow development process is due in part to the large number of people submitting poorly written patches or no patch at all, leaving the Rails community to figure out the problem for them.

Using their new procedure for submitting patches might help to speed things up. One of my patches was accepted just 2 hours after I submitted it.

I think they could also significantly speed things up if they’d migrate to a distributed version control system (whether it’s git, mercurial, bzr, etc). Almost anything is better than subversion.

]]>