Functional and Object Oriented Programming(jmolly.com)
jmolly.com
Functional and Object Oriented Programming
http://www.jmolly.com/2012/06/24/functional-and-object-oriented-programming.html
7 comments
OO idioms and practices encourage coupling. For example, in Java, if you want behavior you are forced to create a class. In OO instruction classes are often introduced as containers of state. So it’s no surprise that in OO systems you typically find data and behavior mashed together.
Replace class with arguments and you have the same "coupling"
As soon as I get the creative idea of asking if my Cat is of drinking age, I can’t reuse this behavior
Yes you can, you just delegate the behavior to an object whose job it is to determine things about ages. It isn't much different than having a suite of related functions designed to operate on things with ages.
We'll designed software doesn't look much different if you do it in a functional or OO language. The main difference you do see is that much of the code for dealing with state disappears in an OO language as the language itself implements it. In a functional language you have to build your own OO like system to make the stateful parts easy.
Replace class with arguments and you have the same "coupling"
As soon as I get the creative idea of asking if my Cat is of drinking age, I can’t reuse this behavior
Yes you can, you just delegate the behavior to an object whose job it is to determine things about ages. It isn't much different than having a suite of related functions designed to operate on things with ages.
We'll designed software doesn't look much different if you do it in a functional or OO language. The main difference you do see is that much of the code for dealing with state disappears in an OO language as the language itself implements it. In a functional language you have to build your own OO like system to make the stateful parts easy.
The original vision behind OOP wasn't at odds with functional programming. In fact, it looks more like modern FP than modern OOP, with its FactoryFactories and POJOs and cargo cult bullshit that are more an artifact of a failed attempt to commoditize programming talent (one which hijacked OOP) than anything else.
Pure functional programming is great. Alan Kay would agree. However, the world is stateful. The original inspiration for OOP was the cell, which encapsulates complex physical machinery (state and behavior) behind a simpler chemical or electrical interface. The idea wasn't that complexity is a good thing (it's not) but that, when it becomes inevitable, it needs to be sequestered so that it's only visible to the few who need to fuss with the object's internals, not to the many who need to interact with it at an API level only.
An "object" is a complex entity whose interface is designed for simplicity. An example of this would be a SQL database. Query optimization is complex, but the interface is much simpler. You don't micromanage which indexes it uses and when; you just specify the query you want to run and trust the software to figure it out. In spite of its age, SQL is the most successful DSL ever invented, and for a number of reasons, but it's relative simplicity and flexibility are high among them. An added benefit of the simpler interface is that implementations can be swapped out without rewriting the entire interface.
Where OOP broke horribly was when someone got the (wrong) idea that every program needed to be "object-oriented", and OOP went from a set of tools solving specific problems (e.g. GUIs) very well to a general-purpose programming paradigm, which became worse because it was so poorly understood. It evolved from a stance of "use objects when complexity requires it" to "use objects as the fundamental unit of programming", which is bad because complexity and uncertainty aren't inherently good, but undesirable all else being equal.
Scheme is a better first substrate for programming than Java, because the fundamental building block of programming should be the referentially transparent function. Only when this is reasonably well understood should people be exposed to mutable state.
Pure functional programming is great. Alan Kay would agree. However, the world is stateful. The original inspiration for OOP was the cell, which encapsulates complex physical machinery (state and behavior) behind a simpler chemical or electrical interface. The idea wasn't that complexity is a good thing (it's not) but that, when it becomes inevitable, it needs to be sequestered so that it's only visible to the few who need to fuss with the object's internals, not to the many who need to interact with it at an API level only.
An "object" is a complex entity whose interface is designed for simplicity. An example of this would be a SQL database. Query optimization is complex, but the interface is much simpler. You don't micromanage which indexes it uses and when; you just specify the query you want to run and trust the software to figure it out. In spite of its age, SQL is the most successful DSL ever invented, and for a number of reasons, but it's relative simplicity and flexibility are high among them. An added benefit of the simpler interface is that implementations can be swapped out without rewriting the entire interface.
Where OOP broke horribly was when someone got the (wrong) idea that every program needed to be "object-oriented", and OOP went from a set of tools solving specific problems (e.g. GUIs) very well to a general-purpose programming paradigm, which became worse because it was so poorly understood. It evolved from a stance of "use objects when complexity requires it" to "use objects as the fundamental unit of programming", which is bad because complexity and uncertainty aren't inherently good, but undesirable all else being equal.
Scheme is a better first substrate for programming than Java, because the fundamental building block of programming should be the referentially transparent function. Only when this is reasonably well understood should people be exposed to mutable state.
Pure functional programming is great. Alan Kay would agree.
Alan Kay does agree: "the greatest single programming language ever designed" - Alan Kay, on Lisp (http://paulgraham.com/quotes.html).
Alan Kay does agree: "the greatest single programming language ever designed" - Alan Kay, on Lisp (http://paulgraham.com/quotes.html).
He actually goes a bit further[1]:
"Lisp isn't a language, it's a building material."
- Alan Kay
[1] http://paulgraham.com/quotes.html)
"Lisp isn't a language, it's a building material."
- Alan Kay
[1] http://paulgraham.com/quotes.html)
Except Lisp isn't a pure functional programming language. It has side-effects, no?
Some Lisps are more functional than others. You're right though, a purely functional language has no side effects, but this is sometimes used loosely. To draw on another quote, this time from Rich Hickey, "A purely functional programming language is only good for heating your computer" :)
>and OOP went from a set of tools solving specific problems (e.g. GUIs) very well
Ironically, GUIs are the least OO thing OO-only languages like .Net do these days with their callback strategies.
Ironically, GUIs are the least OO thing OO-only languages like .Net do these days with their callback strategies.
> The original vision behind OOP wasn't at odds with functional programming.
This!
Imho, Scala shows very well that OOP and FP can be unified without much problems, if enough care is taken.
This!
Imho, Scala shows very well that OOP and FP can be unified without much problems, if enough care is taken.
Is learning Haskell even practical yet? I have a great interest in becoming a more productive programmer, but not as much in learning a language just for the fun of it. What kind of stuff is Haskell best suited for building?
Clojure is functional and practical -- you get access to all of Java's libraries without the performance hits from languages not originally designed for the JVM, like Jython and JRuby.
DrinkingAge.isAbove(person.getAge())
Sounds like the type of code Yoda would write if he codes.
Sounds like the type of code Yoda would write if he codes.
i've being dalliancing in haughtiness for years.
In my mind, the difficulty lies not with OOP per se, but in the thought-patterns and practices that have grown up around modern OOP programming, and the mental confusion that we have between the construction of models, the design of algorithms, and the creation of machines to help solve a particular problem. To a large extent, we lack the intellectual tools required to understand the problem; or, at least, the use and understanding of those tools is not widespread.
Personally, I suspect that there is a significant difference between product-centric thinking (design the product, ignore all else), and product-line-centric (or capability-centric) thinking (design the machinery that will make it trivially easy to design the product). This, for me, is a more important distinction than OOP vs FP, or any other dichotomy that you might care to mention.
I am not suggesting that I am right here, mind you: this is just the way that I feel; my gut instinct ... so perhaps some Socratic questioning might be in order here:
Let me start.
What problem, as software developers, are we actually trying to solve?