Re:Why developers should be force-fed state machines
by lgeek on Monday June 13, 2011 @02:39PM
(#2650180)
I've always thought that gem's a bit silly. It makes sense to think in terms of state machines, but to code them explicitly?
[ Parent
| on HN ]
Re:Why developers should be force-fed state machines
by pygy_ on Monday June 13, 2011 @03:33PM
(#2650378)
Yet another misteriously killed post, by someone who's not deadbanned:
In [1] , fleitz [2] wrote
Explicitly using a state machine often yields benefits in terms of reusability and clarity. The state machine pattern also works really well with async code where it quickly becomes unapparent what's going on.
[1] http://news.ycombinator.com/item?id=2650347 [2] http://news.ycombinator.com/user?id=fleitz
Re:Why developers should be force-fed state machines
by 6ren on Monday June 13, 2011 @10:53PM
(#2651624)
Weird, that's one of the most insightful comment here. Why would it be killed?
Re:Why developers should be force-fed state machines
by Stormbringer on Monday June 13, 2011 @09:48PM
(#2651494)
The same can be said of any of the lesser patterns. People who turn _everything_ into a Singleton for instance. Or who want everything to be a Factory or a Command.