I use OO when the situation merits, just as I will occaisionally use sed when the occaision merits. I do think that OO has some dashed nice things in it, if it's done right. If it's not, it becomes such a headache. This is why I vastly prefer Objective C to any other OO language, at least as an OO language. The whole package (IDE, language, etc) is splendid.

If I may go into "grumpy old pfhardt" mode, I have worked with some fresh-from-college whippersnappers who can evangelize about OO and all that rot, but when you ask them something about real-world programming (like, say, dealing with user input errors), their jaws drop, the saliva begins to drip, and in my mind I hear "Duh, gee, Tennesse, let's ask Mr. Whooppee." Well, that or "Gosh, Mr. Obvious; I never made the connection." I think that, because the OO paradigm hides many things, they sometimes have trouble dealing with things that shouldn't be hidden to the programmer.

--
tbone1
As God is my witness, I thought turkeys could fly.