
Provides information on creating Web-based applications with Rails 3.2 and Ruby 1.9 and each of the examples has been tested with Ruby 1.8.7, 1.9.2, and 1.9.3.
I learned Ruby and Rails through them in the late 2000's; they are still being released as new editions. It has been a while since I bought new books from PragProg, but they used to have a recurring sale of ~40% off around late autumn (thanksgiving?).
[0] https://pragprog.com/titles/ruby5/programming-ruby-3-3-5th-e...
[1] https://pragprog.com/titles/rails8/agile-web-development-wit...
The Ruby on rails channel on YouTube has a playlist explaining all the new components of rails 8 called rails 8 unpacked. Things like solid queue/cache and propshaft.
It's the book I learned originally Rails with more years ago than I care to remember (pre version 1!).
Sustainable Rails is really more about how build bigger projects over the longer term.
i.e. good practice for reducing the churn on model files when you have a larger teams or how to do things with a miniumum of external dependencies.
It's great stuff but you can probably pick that up later if you want to.
BTW I just saw this in browser tutorial from learning Rails[1]. I've not run fully through it but it looks really promising to me.
I was a kid, and read the first two books 14 years ago. One on a holiday in Kenya and the other in Egypt. No distractions, just travel, family and reading.
These days it seems like a lot of junior developers want to learn it more interactively. I hope books stay popular. In my opinion, they do a great job at explaining the why & the reasoning, instead of just showing you how.
Nonsense! I've been around since the 90s too and let me tell you - you don't need any of the trendy new crap to make a successful app. You don't need a single page JS app except in very specific circumstances. You don't need microservices or serverless or map/reduce or Cassandra or NoSQL or nodejs or ML or any of it.
Ignore all that noise, go pick up "Agile Web Development with Rails 6" and just do it. Haters gonna hate but if it's good enough for github it's very probably good enough for you.
