> By clearly defining the transitions from one state to another and when outputs can occur I see state machines as making it easier to develop modular applicati

> By clearly defining the transitions from one state to another and when outputs can occur I see state machines as making it easier to develop modular applications. I don't see how it inevitably leads to non-modular code. I have not seen a modular state machine yet. Perhaps it is possible, but it doesn't seem to be done very often. > If you're modeling a process then some things can't be abstracted. At some level you have to deal with real world situations. I don't think state machines are usually the most natural representation of a process. And very often, people use state machines to model things that don't really fit into that model. > That's a function of the effort made to make it easy to read. It's no different than any other situation. Perhaps I have only seen the bad apples.