Explore >> Select a destination
|
You are here 
|
raphlinus.github.io | ||
| | | | |
eli.thegreenplace.net
|
|
| | | | | ||
| | | | |
www.jeremykun.com
|
|
| | | | | A lot of people who like functional programming often give the reason that the functional style is simply more elegant than the imperative style. When compelled or inspired to explain (as I did in my old post, How I Learned to Love Functional Programming), they often point to the three "higher-order" functions map, fold, and filter, as providing a unifying framework for writing and reasoning about programs. But how unifying are they, really? | |
| | | | |
hookrace.net
|
|
| | | | | ||
| | | | |
lwn.net
|
|
| | | Statically typed programming languages can help catch mismatches between the kinds of values a [...] | ||
