Why are you even reading this book? Rails is old and busted. Everybody knows that Node.js is the new hotness.
Just kidding. Rubyists and Rails programmers alike could learn a lot from Node, but Rails is a slow burn, an old hotness that hasn’t petered out yet.
Really, the question isn’t “Why are you even reading this book?” The horrifying thing about this book is that you probably won’t read it. The question, really, is “Why aren’t you reading it?” What I hear is that this book’s supposed to be a reference for intermediate to expert Rails programmers. This is not how I approached it at all.
I got started in Rails in December of 2005, when it was brand spanking new, but by 2010 or so, I had forgotten a lot of what ...