|Issue 227 – May 29, 2017|
Well, I think the (very minor) drama has settled down surrounding Clojure. You can read some people’s thoughts in this week’s links.
Frankly, all of the discussion wore me out 🙂 These kinds of discussions are important for a community to have. With all of the side-discussions I’ve had that have resulted from the mainline discussion, I’m confident the community will be better off because of it. I’m still not ready to announce anything yet, but I’m excited about the things that are brewing. Meanwhile, Clojure is still awesome, lots of jobs are popping up, and people are happy using it.
Please enjoy the issue.
PS Want to get this in your email? Subscribe! PPS Sorry about the empty email from yesterday. My bad!
From amidst the tumult, I did manage to record a very nice lesson about filtering lists live with Reagent components.
Arne Brasseur responding to the drama with some deep introspection into the community.
Well, here are my thoughts on what’s going on.
Nikita Prokopov talks about recommendations for readable code. I love this. We don’t talk enough about code.
Zach Tellman reflects deeply about the meaning of open-source.
There’s nothing like a minor community crisis to get me thinking about Lisp’s long history. This essay is one of those. It explores how the power of Lisp might be its own undoing.
I had the pleasure of being interviewed on the excellent podcast called “Developer on Fire”. I talk about Clojure, how computing relates to the real world, and my tips.
Yet another self-reflective link. In this talk, Haseeb Qureshi asks an important question: why don’t we converge on “one true way” in software engineering? Many fields do converge, but in programming it seems that we are destined to argue forever.
Okay, last self-reflective article, I promise. This one is about the type of people who are attracted to Lisp. I don’t necessarily agree, but I also see a bit of myself in the person Mark Tarver describes.