S'alright a pure functional toaster just spits out yer bread untoasted.
A pure functional toaster would work one of two ways:
1) It would just be a solid box with no openings. Inside would be full of wondrous magic, but interacting with the outside world involves side-effects so interaction would not be allowed.
2) It would have a glass panel on the side, which you'd hold your untoasted bread against. A slice of toasted bread would pop out of the top. You'd never know where it came from, but you'd be happy that your original slice hasn't been modified.
Keep going, I want to hear how monads get mapped into the world of toast. :-)
You can think of monads as abstractions that may or may not return toasted objects.
Re:The Object-Oriented Toaster (1997)
by arethuza on Wednesday December 02, 2015 @05:09AM
(#10662028)
So maybe toast?
Only for a moment. An extensible claw would fly out, grab the untoasted bread from your hand and fling it into the garbage can, after a brief but unpredicatable interval.
Object oriented analysis and design, done well, is not bad: it is good. It's not wrong to design a class, even a hierarchy of classes perhaps, for a toaster program. Whether doing so is helpful or harmful really does depend on the functionality and complexity of the toaster and the skill of the class designer.
So: sure, bad software design is bad. Thanks for pointing that out. But if the implication is that all (or most or "usual") object oriented design is necessarily bloated, overworked, and excessively forward-looking, then no: only when it, like overcooked bacon, is done badly.