Re:Why Developers Never Use State Machines
by ErrantX on Thursday September 01, 2011 @11:19AM
(#2950351)
Hoi! I am an EE "cast off" :)
But, yes, you are probably right. When I was taught embedded systems we did do software work, usually on small memory footprints, and state machines were what was taught.
Re:Why Developers Never Use State Machines
by snikolov on Thursday September 01, 2011 @02:09PM
(#2951100)
So they suck in a bad implementation choice because it looks pretty to them
An implementation choice that looks pretty is often a good implementation choice.
Re:Why Developers Never Use State Machines
by ajross on Thursday September 01, 2011 @03:24PM
(#2951375)
Except, as I was careful to point out, when it's bad. I hoped my example was useful: people think the OO hell ("class Point", "class Length", ...) in Java is "pretty" too. Aesthetics are squishy. It's easy to point to great code and infer that it's beautiful to other great coders.
But that doesn't change the fact that most people have pretty awful taste. The affinity of uC hackers to state machines, IMHO, is a good example of this.
So they suck in a bad implementation choice because it looks pretty to them. Not so different than the way most Java development works, honestly.