Maybe you’ve heard all the hype about serverless computing. Maybe you’ve heard disturbing rumors that serverless apps do in fact run, somewhere, somehow, on servers. Maybe you were ok with all that, but not with writing AWS Lambda functions in Java or JavaScript. Me too. Let’s do it in Clojure.

Listening to game three of the National League Divisional Series between the Washington Nationals and Los Angeles Dodgers today on the way to the airport, I heard a startingly weighty statistic: The team that wins game three of a five-game series wins 77% of series! That’s one pivotal game!

I’ve been experimenting with clojure.spec on a new web project, as a way of validating data coming in from the client. We’re using JSON API as the lingua franca between the server and client, which adds a not-insignificant amount of ceremony and overhead to the JSON payload. So once I got one namespace’s endpoints spec’ed correctly, the obvious next step was to generalize it with a function that looked like this (edited for brevity):

Tonight I gave a talk at Clojure PDX on building desktop apps with Electron and ClojureScript.

Building QT and capybara-webkit has always been at best an exercise in yak shaving and at worst an exercise in wizardry, prayer, and laptop damage. For the most part I have been free from problems with it for a while, but a new problem cropped up the most recent time I upgraded my Ruby version and bundled a project that included it: