It's definitely that, but to be fair the problem is caused by classg-based programming, not OOP itself. Put state on an object only if there is a hard requirem

It's definitely that, but to be fair the problem is caused by classg-based programming, not OOP itself. Put state on an object only if there is a hard requirement for it. The occurrence is incredibly rare, state is mostly introduced to save re-typing method arguments...