3 ms·

That's assuming that what's in this book is exceptional (which you can't tell without a preview). I didn't think that Practical Object-Oriented Ruby was incredi

That's assuming that what's in this book is exceptional (which you can't tell without a preview). I didn't think that Practical Object-Oriented Ruby was incredible, though it is a well-written tutorial of basic OO techniques. You could spend less than $49 on a couple good used copies of OO classics, or many more if you visit the right used bookstore. And it's not even a hard copy so it is competing with the wealth of good free information online about OOP. I might pay $99 for a hard copy of this, but no way I'd pay $49 for a PDF.

khedoros 10y ago
> I might pay $99 for a hard copy of this, but no way I'd pay $49 for a PDF. Generally, I like physical books more than electronic ones, and I'd be willing to pay a premium for it. From what you're saying, a PDF of the book would provide you < $49 of benefit, while a hard copy would provide you > $99. In your opinion, what is the difference in value between those? What I mean is, what specifically about the hard copy provides enough benefit that you'd pay over twice as much for it? IMO, the greatest proportion of value for a book I'd actually buy is in the information it contains and the presentation of that information, rather than the form it's published in. It's not like I don't have several devices that I could use as portable readers, after all.