The latest rewrite of my book for Rails 4 is available at http://leanpub.com/tr4w
Michael Hartl's Rails Tutorial has also been fully updated. See http://news.railstutorial.org/ruby-on-rails-tutorial-rails-4... for all links to relevant material.
The latest rewrite of my book for Rails 4 is available at http://leanpub.com/tr4w
Michael Hartl's Rails Tutorial has also been fully updated. See http://news.railstutorial.org/ruby-on-rails-tutorial-rails-4... for all links to relevant material.
Design Patterns in Ruby is just as enjoyable.
I have never heard of POODR before...but given that so many people are listing it in the same "top list" as Eloquent Ruby - I am definitely gonna get it.
Hartl's tutorial was a bit much for me. I don't think when I was just learning Rails, to be thrown into TDD was wayy too much and made it much less enjoyable.
I think if there was a "no-TDD" path, it would have been better....or maybe some way to explain the TDD aspect more clearly.
As it is, while one can of course still use Test::Spec, you're likely to be in a small minority.
Since the Book is not 'the factory default stack of Rails' but rather the Rails "way" we certainly do have an opinion about what is considered the most popular and efficient way of building Rails apps. This does mean we use HAML throughout the book, because honestly, we all think its a better choice. Personally, since we converted to HAML at Astrails several years ago, I cringe every time I have to deal with ERB. Its just too verbose and it doesn't present the structure as obviously as HAML. Same for the rest of the 'opinions' in the book. YMMW
I just purchased R4W, looking forward to brushing up.