Re:Functional Programming Doesn't Work (and what to do about...
by anon_d on Saturday July 23, 2011 @12:02PM
(#2797117)
Could people please stop use "Functional Programming" as a
synonym for "Pure Functional Programming"? The author uses
them interchangeably even though his arguments do not apply
to the impure style.
[ Parent
| on HN ]
Re:Functional Programming Doesn't Work (and what to do about...
by chc on Saturday July 23, 2011 @03:01PM
(#2797534)
Even in impure languages, writing simple functions without side effects is the ideal of functional programming — the language just doesn't force it. If you want to write imperative code, just call it imperative. Don't call it functional just because that's the cool buzzword nowadays.
Re:Functional Programming Doesn't Work (and what to do about...
by fuzzyman on Saturday July 23, 2011 @12:15PM
(#2797147)
And whilst we're at it can people stop using "water" as a synonym for "pure water". Mud is water too, it's just not as pure!
Re:Functional Programming Doesn't Work (and what to do about...
by mattdeboard on Saturday July 23, 2011 @05:23PM
(#2797874)
Terrible, terrible, terrible analogy.
The ecosystem of programming languages are analogous to class&race interplay in RPGs, especially RPGs where youve got strong distinctions between melee (imperative) and casting (functional) classes, with a smattering of hybrids (Python, Ruby, Scala, Clojure).
Re:Functional Programming Doesn't Work (and what to do about...
by dlikhten on Saturday July 23, 2011 @12:17PM
(#2797153)
anon_d has a point, im interested in the same take on using scala and other hybrids.
Re:Functional Programming Doesn't Work (and what to do about...
by silentbicycle on Sunday July 24, 2011 @12:43AM
(#2798655)
I think that's his point.
"After spending a long time in the functional programming world, and using Erlang as my go-to language for tricky problems, I've finally concluded that purely functional programming isn't worth it." (emphasis mine)