## Back at it, reading and emails

* TOC
{: toc }

Besides the readings below, I cleaned up my inbox, which I haven't done in about a week, so that feels good to be back in integrity. 

### Jonathan-Edwards-inpsired Reading

I meant to reach out to Jonathan Edwards today (but didn't), and found myself on his twitter, where I found some amazing gems:

* [Against functional programming](https://twitter.com/jonathoda/status/976937603709587456)
* [Near Future of Programming Languages by Stephen Diehl](http://dev.stephendiehl.com/nearfuture.pdf)
* This comment amazing comment: ["Imperative programs, on the other hand, always have a ready axis for decomposition: time. You break your program up into tiny time slices, and then work backwards to find procedures that that get you to the first one, then the second one, etc, until you hit the end of your program."](https://news.ycombinator.com/item?id=16726917) on this [Gradual Programming](http://willcrichton.net/notes/gradual-programming/)
* Conal Elliot: [Can functional programming be liberated from the von Neumann paradigm?](http://conal.net/blog/posts/can-functional-programming-be-liberated-from-the-von-neumann-paradigm) - This article makes me so happy. Monads, and every other approach to IO in a functional language, stinks. We need to keep looking.
* [Why program with continuous time?](http://conal.net/blog/posts/why-program-with-continuous-time) - good summary of the key points of FRP
* ["What next?"](https://graydon2.dreamwidth.org/253769.html) by Graydon Hoare, creator of Rust. Holy shit this article is amazing. So many gems! I want to read this article again and again. Would love to email him and get his advice on where to apply my efforts towards improving programming.

### Graydon Hoare-inspired reading

* From Graydon, I was sent to learn about algebraic effect handlers in [Eff](http://www.eff-lang.org/), which didn't really impress me to be honest. Their pitch of "you know how much you like exception handlers? Let's have more of those" doesn't resonate with me because I never liked exception handlers. Feels to procedural, contextual to me. I much prefer it encoded in the types, such as a Maybe or Failure type. 
* [Koka](https://www.microsoft.com/en-us/research/project/koka/) makes a little more sense to me, labelling functions based on whether it can raise an exception, possibly not terminate, and be non-deterministic... but I only skimmed the beginning.
* I was VERY EXCITED to see [Frink](https://en.wikipedia.org/wiki/Frink_(programming_language) and ["units of measure" in F#](https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/units-of-measure). I've both sad and excited that [this exact idea I've had](http://futureofcoding.org/notes/kill-primitives#4-phsyics-units-for-numbers) has already been had. I claim independent invention! 

### Todos of 5/16/17 in no particular order

* Finish re-watching Conal's [Tangible Functional Programming](https://youtu.be/faJ8N0giqzw?t=32m49s) and try to read [the paper](http://conal.net/papers/Eros/eros.pdf), Maybe I should print it out to help me focus...?
* Also, don't forget [the other ToDos of last week](http://futureofcoding.org/log#some-todos-i-scribbled-down-last-week), especially reaching out to Jonathan Edwards and possibly Sean McDirmid
* Possibly reach out to Graydon Hoare or at least learn more of what he has to say, including re-reading his "What next?"
* Find a better way to manage these notes and todos so things get less lost...?
* Edit (or throw out) [plan v6](https://github.com/stevekrouse/futureofcoding.org/blob/3821ba9d0ad65a7f6aaea583be8283aba16558e5/plan.md)

Author: Steve Krouse