This book can serve as a cookbook and also can double up as a ruby tutorial. Whenever i read a recipe, i'm pulled into at least 2 or 3 of the neighboring recipes too. There's a lot to know about Ruby and this book simplifies the learning, teaching/illustrating one concept at a time.

This book is an excellent reference on the Ruby language. I have this book, the pickaxe, and the cookbook. But the book I always turn to first is the ruby way. The style is excellent- slightly informative with some gems of quotes, like "brother, can you paradigm? -Grafiti seen at IBM Austin, 1989"
I wish all language references were written like this, although I am not sure if it is accessible as a first book on Ruby.

This is a very thorough companion to just about everything in Ruby, starting with the core language features, and then moving onto some of the more important libraries. As such, it has a reasonable overlap with Ruby Cookbook. In most languages, you'd expect the O'Reilly's mighty Cookbook series to come off best, but The Ruby Way edges it in this case. It's that good.

The Ruby Way not only covers more than Ruby Cookbook, it also manages to be a little more cohesive, dispensing best-practices and general wisdom amidst its well-chosen examples. If you already know another programming language, you could probably learn Ruby from this book (in particular, the first chapter contains a great set of reminders and idioms), and it might even be the only Ruby book you'd need.

Apart from its comprehensive coverage of Ruby itself, there's also coverage of important Ruby projects like Rake, gems and Rinda. It even covers more than Rails in its chapter on web frameworks, although it must be admitted that you don't get too much sense of how these really work given the space allotted to them.

One notable characteristic of TRW is that in places, it has a slightly fuddyish writing style, for example, it refers to the use of 'threequals' for the case equality operator as "hip and trendy" (with scare quotes included). I quite enjoyed this. Yes, there are some typos and mistakes in the book, but I didn't find it was a big problem, you can normally work out the correct syntax with the minimum amount of experimentation in irb.

A mighty combination of cookbook and best practices (akin to Effective C++ and Effective Java, although Rubyists probably don't like the comparison to those languages), The Ruby Way is the Must Read of the Ruby literature.

It's a good book for learning the Ruby language, and at almost 800 pages it's one of those books that will usually be sitting nearby (next to the Pickaxe book).

This is a solid Ruby language manual. It has more breadth than the Pickaxe Book, covering more libraries and advanced topics. It also provides more detailed, accurate descriptions of language basics, like exactly how the "case" statement works. I'm still working my through it: it is deepening my knowledge of Ruby.

(Full Disclosure: Long time computer geek)

I bought this book hoping to learn the basics of the Ruby language to keep my skills current. This book surpassed my expectations.

Not only did this book provide me with a solid understanding of key Ruby principles, it made me excited about using Ruby.

Rdoc is great, and deeper than this book, but The Ruby Way is better in terms of examples. O'Reilly books really don't do it for me with Ruby, and I don't even know if they have a Ruby Cookbook, but it doesn't even matter.

This is the only Ruby book I have that isn't from the Pragmatic Programmer's publishing company. I recommend starting with this book, then working your way through the Pragmatic series if you want to get your black belt in Ruby.

As the title says it ... don't look any further ...

This book has a very good design. In each chapter, one aspect of Ruby is explained in great detail. The examples also help a lot on comprehending the language.

Well, as the headline of my review says; It's a MUST-HAVE for the serious Ruby coder.
Whatever the question, you'll find a very compentent answer and a very good explanation in this book.
The author knows his stuff hands down.
It's a pleasure to read the example code and see how elegantly written Ruby can be.
It's a book that should be used by anyone who has doubts about Ruby's power and elegance.

The first edition was already an amazing book, but the second edition really tops it.
Great work!

I wish other computer science book were this concise...

This is a book I could see being really helpful for someone who's done the Ruby tutorial and now needs to actually *use* the language to do something... The Ruby Way (2nd Edition) by Hal Fulton.

Contents: Ruby in Review; Working with Strings; Working with Regular Expressions; Internationalization in Ruby; Performing Numerical Calculations; Symbols and Ranges; Working with Times and Dates; Arrays, Hashes, and Other Enumerables; More Advanced Data Structures; I/O and Data Storage; OOP and Dynamic Features in Ruby; Graphical Interfaces for Ruby; Threads in Ruby; Scripting and System Administration; Ruby and Data Formats; Testing and Debugging; Packaging and Distributing Code; Network Programming; Ruby and Web Applications; Distributed Ruby; Ruby Development Tools; The Ruby Community; Index

Fulton states in the introduction that this book is not designed to be a "teach yourself Ruby" title. Instead, it's meant to explore the power and utility of the language by means of examples. Think of it as a *really* large cookbook-style volume. In each chapter, there are a series of how-to sections that are practical examinations of a particular technique. For instance, in the regular expressions chapter, you'll see sections such as using anchors, positive and negative lookahead, recursions in regular expressions, and detecting doubled words in text. This solutions-based approach to Ruby is perfect for someone who has covered the basics via a tutorial or some other book, but now has to actually use the language to do something. Personally, I find having a book like this is extremely valuable in making the jump from rank novice to functional developer. I know good code when I steal it... :)

I haven't done much with Ruby and decided it was time to dive in. I opened this enormous text and started. The book is broken down nicely into several beginners "howto" sections and then into more of reference and advanced learning portion.

Coming from a Perl programming background I found several things (mostly syntax) in Ruby quite odd and am very happy to have this reference on hand.

The GTK section of the book is very nice as I haven't seen it covered elsewhere. The additional coverage of Rails adds to the completeness of the material and helps the book win some popularity on a current hot topic.

This is a very well-rounded text for Ruby programmers. I would recommend it to anyone interested in learning Ruby, regardless of programming experience.

Yes, there are some typos in Fulton's book. But the vast bulk (and it is indeed a big text) can be profitably read. Either by someone wanting to learn Ruby from scratch or by a Ruby programmer searching for a solution to some common problem. For the former, the book may be too long. If you want to come up to speed on Ruby, ab initio, perhaps you might consider a slimmer text.

The book is best suited as a random access resource, for a Ruby programmer. As implied by the title. The 400 odd examples demonstrate a good diversity of usages of the language. Grouped according to broad topics like threads, user interfaces and networks. This helps you focus on finding a possible solution. However, suppose you can't find an exact match. The numerous examples may have one close enough to suggest an easy mod.

Granted, if a relevant example has typos, so that it won't run, that's a drag. But only a minor one. If you already know Ruby, fixing this should be a low level detail.

As far as comparing with other scripting languages, well the book does not do this. No mention at all of Perl or PHP. Probably the author regards this as outside the book's remit. The decision of whether you should use Ruby over those alternatives is something that cannot be answered by this book alone.

I'm reading the first chapter "Ruby in Review" and it is chock full of typos and mis-usages. This is particularly disconcerting pertaining to the very first sample program; e.g. it contains the statement "str.chomp!" but then the the ensuing explanation alternately refers to "chomp" as well as the previously un-discussed "chop". I'm an experienced Perl programmer and know the difference, but this must be confusing to other readers not lucky enough to have such background. Furthermore, referring to the same "chomp!" operation, the exclamation point is referred to as a prefix. This is incorrect: it's a suffix.

Computer language interpreters including Ruby itself would balk at such imprecision in code instuctions, and therefore I balk at such imprecision in English. It makes me wary that code samples later in the book will contain typos, though I give the book one star more than the minimum because the first sample program as entered in the book does run properly. Still though the editors should be ashamed.

I see this over and over with technical books: the first chapter(s) are flawed with such typos, probably because they get written and reviewed first, several months before the rest of the volume is finished. Further indication of this is the author's comment near the end of the first chapter that he is unaware of other languages with the "===" operator. Perhaps he wrote this for the first edition; by the time he wrote the second edition, particularly with the explosion of Ruby on Rails and Ajax, he should know that Javascript also provides the "===" operator (as does PHP).

In addition, the title of this volume is misleading and pretentious. Ruby suffers from the same "there's MORE than one WAY to do it" approach as Perl (e.g. "poetry mode" that dispenses with parentheses around method arguments). Perl has proven this sort of thing is a drawback, not a benefit. It's derisively referred to as a "write-only" language, and I predict Ruby will be considered likewise after 3-5 years when a sufficient base of Ruby code exists such that Ruby "maintenance" programmers will be in demand.

Furthermore, the author frequently notes how some of these multiple ways to accomplish things in Ruby can "confuse the parser"; there's no arguing this is a drawback. It can only further slow down a language already slow due to its interpreted, dynamically-typed, object-oriented nature.

Tech authors, do yourself a favor, and have somebody (re)edit your initial introductory chapter(s) at the tail end of the process, otherwise risk making a bad first impression. Programmers, do yourself a favor, and don't just blindly jump on the Ruby bandwagon.

Just to say I have almost every Ruby and every Rails book out here,
To me, his one is by far the best.
The writing style is very good, and even if the author says it's not intended as a tutorial, you could definitively use it to learn Ruby from scratch too.

People in the Ruby development community know me because I started several of the most popular open source Ruby projects (I have been active in Ruby since 2001). If you are serious programming in Ruby then there are two must-have books to keep within reach as you program: Dave Thomas' Programming Ruby; and this book: Hal Fulton's The Ruby Way.

This is really two books in the guise of one. One the surface, The Ruby Way appears to be a cookbook of Ruby recipes, and a very thorough one at that. But The Ruby Way also manages to capture the gestalt of Ruby, that intangible, indefinable philosophy behind the Ruby idioms that old-timers now take for granted.

Every programming language has its own "way" of doing things. You don't want to write Java code in Ruby, or VB code in Ruby, you should be writing *real* Ruby code. If you want to see Ruby code the way it was "meant" to be written, this is your book.