[crabmusket]

To the author: if you haven't read POODR, I highly recommend that. It's the book that felt the most "real OOP" to me. No `class Dog extends Animal` in sight. It's written by one of those Smalltalkers, and I think it's got a lot of very valuable ideas about software design, not just OOP specifically.

The "callback-y" approach in Growing Object-Oriented Software sounds fascinating.

> Immediately I remind myself that the implementation from the book ignores the problem of persistence completely. If you close that application it loses all the state. I think this is not an accident. This is where things go wrong for OOP really fast.

This is a really good point.

EDIT: I see you really did not like 99 Bottles of OOP, which is by the author of POODR. In that case maybe her way of explaining things doesn't agree with you and you should skip it!

[Jtsummers]

POODR = Practical Object-Oriented Design in Ruby by Sandi Metz.

[crabmusket]

Thanks. I tend to leave it abbreviated because it's always the top Google result!