"Classes get in the way between the programmer and the problem. ... Functions, for me, are the right level of abstraction to do this. They don't get in the way.

"Classes get in the way between the programmer and the problem. ... Functions, for me, are the right level of abstraction to do this. They don't get in the way." Couldn't agree more. I've long suspected that OO is a diversion or misdirection from actually solving the problem, rather than an inherent part of it. Discovering functional programming recently with Scheme and then Haskell has only reinforced that. OO may be the appropriate abstraction for some things like GUI programming, which seems to be what it was originally created for, but not everything.