I have find this article Turning Your Code Inside Out and I want to know how this approach described in article is for OO programmers/languages.
Is this style of design used in OO programmers/languages? What's downsides and goodsides of this approach in a OO language?
OO objects have state and behavior, the design explained in article is stateless. Is not only Single Responsability Principle.
(If I'm talking shit, please explain to me instead of only downside/close votes)