Co-Author here: I'm part of the team that is helping write The Rails 4 Way. Just to address your concerns, we have gone through the existing manuscript and removed everything that isn't best practice today. On top of that, we are covering all the new Rails 4 features, and important gems/techniques valuable to a Rails developer today. The second half of the book is going through a big revamp right now. Look for updates in the coming weeks.
Ah that's it. I'm going through mhartl's Ruby on Rails Tutorial and he has us specify a Rails version to maintain consistency btw the tutorial and our code.
Maybe a typo? A search for 'ruby rails stimulus' brought me right back to the root comment. About to listen to the podcast. Will report back if I learn anything.
Not sure this is what you're getting at. I agree with the author though, this aspect of Rails bothered me quite a bit. Knowing that working on a Rails project meant I could magically generate ranges from dates because of ActiveSupport was unsettling - it made me wonder what else was non-native behaviour and waiting to trip me.
It ought to mention this somewhere, no? Otherwise I suspect some people might feel they'd wasted 5 hours learning a possibly-soon-to-be-outdated technology. (This would be less important for Rails, say, where the changes between 4 and the next major release - or even between 3 and 4 - would be less drastic.)
reply