Re:Disadvantages of purely functional programming
by theseoafs on Sunday June 05, 2016 @12:44PM
(#11841781)
> Huge body of problems can be handled by simple recursion but I've yet to see non-functional programmers use it. I don't know why.
Stack overflows.
Re:Disadvantages of purely functional programming
by Mathnerd314 on Sunday June 05, 2016 @12:56PM
(#11841844)
"Functional" languages typically have tail-call optimization and heap-allocated frames. Maybe OOP is a workaround for these missing features...
Re:Disadvantages of purely functional programming
by braythwayt on Tuesday June 07, 2016 @09:13AM
(#11854209)
Why doesn't your language have TCO?
"Nobody uses recursion."
Why doesn't anybody use recursion?
"No TCO."
Re:Disadvantages of purely functional programming
by pmarreck on Sunday June 05, 2016 @01:15PM
(#11841935)
Tail-call optimization eliminates those. Assuming your language provides it, and assuming you trigger it correctly. ;)
http://stackoverflow.com/questions/32164370/does-elixir-infi...
Functional style is simply better and is applicable in many languages. Modern C++ is a great example. Throw away much of OOP clunkiness, use simple functions, win! (OOP has it's place but in small quantities and with moderation).
With respect to purity I'm on the sidelines. I think what's far more important is algebraic data-types, pattern matching and value-returning conditionals (values, not statements!). Rust has them and it is great and not pure.