[iamdave]

This is the way absolutely every book that aims to teach people a language should be written. When Ruby on Rails hit it big, I picked up two books and couldn't get past the first two chapters.

Why?

The first two chapters were filler chapters. The history of ruby, the history of taking application languages and putting them on the web. An entire quarter of the book in pages was full of back-story, it was chapter 4 before I even saw any code, and chapter 6 before the actual instruction even began.

I will certainly buy this book, and if Zed produces any more about other programming languages in this format, I'm buying them too.

[zedshaw]

Thank you, I hope it works out that way. I may do other books, especially since this is turning out to be easy enough to do. First though I need to write this one.

[DannoHung]

Okay, but why were you trying to learn Ruby from a book about a web programming framework for Ruby?

Did you try reading the PickAxe or Why's Poignant Guide?

[Pistos2]

He didn't say he was specifically trying to learn Ruby.