Why do programmers these days hype the functional programming paradigm so much? All the functional code is translated to machine code anyways, which is imperative by design.
What are the upsides of using "functional programming" when the libraries and compilers used for it are all written in imperative languages like C++ anyways?
If anything, repeatedly creating new immutable data structures (such as lists) instead of just appending items to the end seems like a waste of memory and time. Most programmers don't think like autistic mathematicians anyway, so imperative style is much more intuitive.
The paper "Out of the Tar Pit" explores the problems with imperative programming, and the advantages of functional/logic programming, pretty well. It's not exactly short at 66 pages, but it's an easy read compared to many academic papers.
Link:
http://shaffner.us/cs/papers/tarpit.pdf
It's just more circle-jerking with a bunch of scraggly hobo programmers going "look how complicated my code is! Bet you can't figure out what this statement means! Codder like you mean it, fellas!" like any other language.
Functional is probably good for AI programming. Anything else is fucking ridiculous.
>>58034313
because
#include<iostream>;
cout<"lul";
is easier than
010111111111101000000000001101010101011010101010101010000000000111000001101010101000101011000000000001010
>CS grad tries to make fizzbuzz in Idris to show how smart he is
>Fails miserably
>Complains about how functional programming languages are bad
>>58034313
You might want to look at the way Clojure implements immutable data structures, it works around the issue you raised in quite a clever way. https://www.youtube.com/watch?v=wASCH_gPnDw
>>58034313
Writing lambda functions in C++ is nice.
>>58034313
It works around the threading problem.
>>58035289
this is wrong so many ways