Agile Web Development with Rails 4

by Sam Ruby, Thomas Fuchs, David B. Copeland, et al.

Book Overview

Rails just keeps on changing. Both Rails 3 and 4, as well as Ruby 1.9 and 2.0, bring hundreds of improvements, including new APIs and substantial performance enhancements. The fourth edition of this award-winning classic has been reorganized and refocused so it's more useful than ever before for developers new to Ruby and Rails.

Rails 4 introduces a number of user-facing changes, and the ebook has been updated to match all the latest changes...

• Format: Paperback
• Language: English
• ISBN: 1937785564
• ISBN13: 9781937785567
• Release Date: November 2013
• Publisher: Pragmatic Bookshelf
• Length: 458 Pages
• Weight: 1.82 lbs.
• Dimensions: 0.9" x 7.6" x 9.0"

Customer Reviews

All Technical Books Should be Written Like This One

As a web developer, I own literally hundreds of technical books - most of are either thick tomes full of encyclopedic information you'll never use in real life. This book is perfect for learning rails. You jump right in and develop an application - getting a taste for what you'd be doing in real life right away. Datailed explanations are left for later, when you better understand how the platform actually works. The example application you'll develop, if you follow the book as you should, is a real-world shopping cart type app. Along the way you'll pick up some agile development. I would not recommend this book to absolute beginners to web development - you should understand some basic web development. This book takes you through everything from installing rails and MySQL to deployment.

The real agile way to develop web applications

Rails, or more appropriately Ruby on Rails is the new web application development framework that everyone is so excited of and raving about how it cuts development time by a factor of 10 and does away with the cumbersome XML configuration files that are the hallmark of J2EE. Being an old Java hand, I wanted to see firsthand if there was some substance beneath all the hype. I was also intrigued by the fact that many other old Java hands whom I respect and admire, like James Duncan Davidson, Elliotte Rusty Harold, Bruce Tate, Graham Glass, and Brian McAllister are now fervent (to different degrees) rubyists and Rails-enthusiasts. If it weren't for them, I would never have undertaken this journey, probably. But anyway, this is supposed to be a book review, not a chronicle of my ongoing discovery of Rails. I mostly like using books to discover and learn about new technologies, so it's perfectly natural that I decided to take off with what is considered the book about Rails. And how could it be not, with Rails' creator David Heinemeier Hansson as one of its authors? It is also the only one published so far but, even though the choice was a bit, uhm ... limited, I wasn't disappointed. The book, as is customary with titles from The Pragmatic Programmers' bookshelf, is very good. It lays down in detail almost everything you need to know to be productive with Rails, save for the language Ruby itself. To be honest, the book includes an appendix introducing the basics of Ruby, but it's just the bare minimum. I suggest getting yourself a good Ruby book (like Programming Ruby, also from The Pragmatic Programmers, which I am currently reading and will review shortly) if you really want to get the most out of Rails. Another caveat you have to be aware of is that Rails is a quickly moving target. The book covers version 0.13, which was current around mid-2005. There was a 0.14 version after that and we are now at 1.0, since a few weeks ago. However, I didn't find I had much to change while experimenting with Rails following the book. As always with Open Source software, resorting to the mailing lists, forums or the #rubyonrails@freenode.net IRC channel is the best avenue for finding answers to your doubts and asking support questions. The book is organized in four parts: Part I introduces the design principles behind Rails, its most important concepts and briefly covers how to get started by installing it and writing your first program. The part about installation is the one that is bound to become quickly obsolete, as new and easier installation methods for the various supported platforms are developed. Part II dives into Rails by guiding you along the development of a real (albeit much simplified) e-commerce application. I find this approach to be very good and "pragmatic" indeed. Of notable interest is the chapter on testing. It's great to see that providing a good test scaffolding was one of the main design concerns in Rails and not just an afterthou

Excellent

I just finished researching and assessing the use of Rails (a.k.a. Ruby on Rails). The primary technical resource for this research was the book, Agile Web Development with Rails by Dave Thomas and David Heinemeir Hansson. As you probably already know, Dave Thomas of Pragmatic Programmer fame is a delightful writer and David Hansson is the guy that created the Rails framework, so I expected the book to be good, but not this good. In my opinion, this is one of the best development books I've had the pleasure of reading in a long time. I found myself reading almost the entire book - which is unusual since I normally can't get past a few pages in most technical books before labeling it crap and putting in the circular bin. (I do not donate those books to the library because I don't want to encourage their distribution). In my opinion, Rails is a really important lightweight framework for developing green-field web applications that don't require the heavy lifting associated with 2PC and support for legacy systems. If you want to be on the cusp of the next frontier in web and enterprise development, you should start with this book which will introduce you to Rails, Ruby, and a new way of thinking about web development in the enterprise.

The best way to learn Ruby on Rails

This book was in development through July 2005 and provides a timely introduction to the excellent web framework Ruby on Rails. Rails is a full stack, open-source framework in Ruby (see rubyonrails.com). I can think of no better way of learning Rails than buying this book (and Programming Ruby, "Pickaxe 2", if you are a Ruby newbie) and working through the hands-on bookstore building exercise in a weekend. "Agile" development takes center stage, as you might imagine from the title. Because of the dynamic nature of Ruby and the way Rails extends the core language, Ruby on Rails lets you easily modify, run, and test web apps. The first part of the book (Chapters 4 to 12) shows how to develop a bookstore app in an iterative fashion. A mock client asks for improvements and the authors show how you build a web app that meets the client's needs. A number of best practices have been distilled from other languages/platforms, and you'll see how they come together coherently in Rails. The Model-View-Controller (MVC) pattern for separating data, presentation, and business logic. Integrated testing. Ways to not repeat yourself across code and configuration files. Active Record pattern for handling data sources. In addition to what's taken from other platforms, the Rails developers extensively use the metaprogramming features of Ruby to wrap these best practice ideas in a nice domain specific language, and this book gives you a good overview of the Rails web app language. "Convention over configuration" is another key to Rails development, and a number of figures show the Rails convention in directory layout, naming, and URL mapping. Although the book is very accessible to Ruby newbies (in part due to an appendix that provides a quick intro to the language), it assumes some knowledge of core Web technologies. You should be acquainted with HTML and databases (like MySQL). The sweet spot for this book might be PHP, Java, and .NET web programmers. The third part of the book drills down into Rails. You'll learn all about the Active Record object-relational mapping layer, and how easily you can specify relationships, validations, and structures like lists and trees. Other chapters focus on the controller and view portions of the MVC approach. The integrated "AJAX" (asynchronous javascript) support gets a chapter, as do e-mail (Action Mailer) and web service support. The book concludes with a couple of chapters on security and the best ways to deploy and scale your web app. This book was written in an agile fashion; I can't remember another computer book that was in print a single month after editing was finished. Despite the speed of publishing, the book can't hope to cover all the new developments given the momentum of Rails. What won't be in the book but might be useful to Rails programmers? SwitchTower is a new utility to automate application deployment (among other things), and ActionStep will be a Rails-friendly framework for writing rich GUIs that target

Excellent introduction to a fascinating framework

Ruby on Rails is a pretty young technology. Its first release was midway 2004, and it has been gathering momentum since late 2004. It has yet to see its official 1.0 release. So it is a pleasant surprise that there already is a book available (electronically since June 2005), and that it such a good book! Why read this book? Since Dave Thomas' credentials as a technical writer are well established (pick up The Pragmatic Programmer if you haven't got it already), this question boils down to: why learn more about Ruby on Rails? For me, the answer was that I have long been looking for a simpler way to build web-applications. I'm a J2EE developer, and it seemed that every project I joined had a different set of frameworks. All of those frameworks could be configured to work together, and there are even frameworks whose only purpose is to make other frameworks work together. There are tools that generate stubs to wrap frameworks, and frameworks that wrap other frameworks, so that the developer needs not know what the underlying framework is. Madness. Rails behaves as if it were one framework. Configuration is simple (no xml) if you need it at all, since the defaults are pretty smart. Writing tests for your model and your controllers is actually easy. The API documentation is very good. Instead of mucking around with frameworks, you find yourself thinking: What do you want to do today? Drawbacks: Is Ruby on Rails slow? Performance is acceptable, I think, especially considering that web applications are database-bound. Rails also scales well - and anyway, processors are cheap, brains are not. Is Rails proven technology? Clearly it's not, it's the new kid on the block. More seriously, Rails is still in flux - the core api is still changing, and it could still take some time to settle down. So now is not the time to start huge Rails projects, now is the time to learn rails and build prototypes and small projects. And with that, this book will be a tremendous help.