I think you've got it wrong. The degenerate case of this is that you've one object, called a "Computer", which can "compute". We live in a world. It has state.

I think you've got it wrong. The degenerate case of this is that you've one object, called a "Computer", which can "compute". We live in a world. It has state. Something needs to manage, check, and hold the state. It's sometimes easier to conceptualize a problem by pretending that state doesn't exist, but it's an abstraction that leaks badly for anything that does not exist in isolation from the world. The misconception that wrecks OOP in the eyes of many is that OOP == "Class Hierarchy". OOP = "Objects" and "Messages". Everything else is negotiable.