Explore >> Select a destination
|
You are here 
|
danielpecos.com | ||
| | | | |
128bit.io
|
|
| | | | | In my last post, I said I was in Italy on vacation and you may be thinking to yourself (most likely not, but just go with it) "what high tech gizmos did he bring with him on his travels?" and I would happily reply "A book!", yes a paper book. Being a software developer, I have access to tons of technology, more so when it comes to paper book replacements but there is just something about a real book that makes reading and learning for me better than using a computer, tablet, or doohickey. | |
| | | | |
initialcommit.com
|
|
| | | | | In this article, we'll discuss Scheme and why we feel it is the hardest programming language to learn. We will also discuss a few other difficult programming languages. | |
| | | | |
sookocheff.com
|
|
| | | | | I previously talked about what functional programming is by comparing it to other programming paradigms. This post expands on that post to talk specifically about practical differences between functional programming and the paradigm most of us are intimately familiar with - imperative. This post is punctuated with some quotes from the book An Introduction to Functional Programming Through Lambda Calculus. It's worth noting that each of these practical differences are enabled because of the power of referential transparency. | |
| | | | |
degoes.net
|
|
| | | Effect tracking is not a non-goal for commercial software development; the real reasons to use functional effect systems lie elsewhere | ||
