Comments on: Rails 1.2: No More Excuses! http://www.sitepoint.com/blogs/2007/01/31/rails-12-no-more-excuses/ News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com. Fri, 21 Nov 2008 10:34:36 +0000 http://wordpress.org/?v=2.5 By: mpdesigns http://www.sitepoint.com/blogs/2007/01/31/rails-12-no-more-excuses/#comment-264026 mpdesigns Fri, 01 Jun 2007 18:17:13 +0000 http://www.sitepoint.com/blogs/?p=1845#comment-264026 Where is the writer for this blog? Lots of things are happening in the Rails community and not a bit of it would be known via Sitepoint. Come back please! :( Where is the writer for this blog? Lots of things are happening in the Rails community and not a bit of it would be known via Sitepoint. Come back please! :(

]]> By: mwmitchell http://www.sitepoint.com/blogs/2007/01/31/rails-12-no-more-excuses/#comment-168508 mwmitchell Thu, 01 Feb 2007 02:01:54 +0000 http://www.sitepoint.com/blogs/?p=1845#comment-168508 I've spent the last few weeks porting a php app to rails. Sadly, I'm out of time and have to go back to the PHP version. Now I'm coding PHP differently/better, but really miss Ruby. Ruby is just, well plain great! One thing that got me, was how are people creating back-end sites (the admin app) using REST and Rails? I tried doing it following the convention of using one controller per resource, but it ended up getting weird and too complicated. All for a much needed back-end. Finally decided to use 2 controllers for each resource, and things worked out OK. Anyway, I highly recommend Rails and Ruby to any PHP programmer out there. It's a breath of fresh air. I’ve spent the last few weeks porting a php app to rails. Sadly, I’m out of time and have to go back to the PHP version. Now I’m coding PHP differently/better, but really miss Ruby. Ruby is just, well plain great!

One thing that got me, was how are people creating back-end sites (the admin app) using REST and Rails? I tried doing it following the convention of using one controller per resource, but it ended up getting weird and too complicated. All for a much needed back-end. Finally decided to use 2 controllers for each resource, and things worked out OK. Anyway, I highly recommend Rails and Ruby to any PHP programmer out there. It’s a breath of fresh air.

]]> By: XraySierra http://www.sitepoint.com/blogs/2007/01/31/rails-12-no-more-excuses/#comment-168197 XraySierra Wed, 31 Jan 2007 16:49:21 +0000 http://www.sitepoint.com/blogs/?p=1845#comment-168197 Defiantly will be buying this book. Nice to see a simple step by step guide for Ruby on Rails. Defiantly will be buying this book. Nice to see a simple step by step guide for Ruby on Rails.

]]> By: Matthew Magain http://www.sitepoint.com/blogs/2007/01/31/rails-12-no-more-excuses/#comment-167899 Matthew Magain Wed, 31 Jan 2007 09:26:14 +0000 http://www.sitepoint.com/blogs/?p=1845#comment-167899 Good point webbie, you are correct. However we decided that for a beginner's book it was less confusing to advocate that the reader install Ruby 1.8.4, rather than introduce using plugins and passing parameters to script/server early on in the book (these are covered in a later chapter). Thanks for mentioning the link! Good point webbie, you are correct. However we decided that for a beginner’s book it was less confusing to advocate that the reader install Ruby 1.8.4, rather than introduce using plugins and passing parameters to script/server early on in the book (these are covered in a later chapter).

Thanks for mentioning the link!

]]> By: webbie http://www.sitepoint.com/blogs/2007/01/31/rails-12-no-more-excuses/#comment-167789 webbie Wed, 31 Jan 2007 07:10:17 +0000 http://www.sitepoint.com/blogs/?p=1845#comment-167789 The fix for the breakpointer issue is actually in the error message in the codebase. See: http://dev.rubyonrails.org/changeset/5381 You might check out ruby-debug (http://www.datanoise.com/ruby-debug), which will allow you to run a Rails app under a debugger including stepping, inspection, and breakpointing along the way. The fix for the breakpointer issue is actually in the error message in the codebase. See:

http://dev.rubyonrails.org/changeset/5381

You might check out ruby-debug (http://www.datanoise.com/ruby-debug), which will allow you to run a Rails app under a debugger including stepping, inspection, and breakpointing along the way.

]]>