For about a decade, I used to speak regularly at conferences and user groups around the world. In 2013, I decided to take a break and just enjoy attending events (here's a small selection of my presentations covering the last three years of that decade).
I've written before about how I switched from Emacs to Atom at the end of 2016, where I initially used ProtoREPL (which is no longer maintained) and then I switched to Chlorine at the end of 2018.
seancorfield/next.jdbc 1.1.610Updated 2022-09-12 to clarify camel-snake-kebab usage in more recent next.jdbc versions.
Wrapping Up 2019It's been a while since I blogged about the projects I maintain so I figured New Year's Eve 2019 was a good time to provide an update!
An interesting Clojure question came up on Quora recently and I decided that my answer to "how do you use clojure.
Lots of ReleasesOver the last week or so I've released minor updates to several of the projects I maintain, so I thought it would be nice to have a summary blog post rather than a scattering of minor announcements.
next.jdbc 1.0.0 and 1.0.1First off, seancorfield/next.jdbc 1.0.0 was released on June 13th, 2019 (and I announced it on ClojureVerse but did not blog about it), and yesterday I released seancorfield/next.jdbc 1.0.1 which is mostly documentation improvements.
Daniel Compton has continued his excellent trend of writing an analysis of the State of Clojure survey comments and one of the comments in his Community section stood out for me:"I suggest moving off of slack to a more accessible chat system.
About a month ago, I was praising Chlorine, the new Clojure package for Atom and I've been using it, day-in, day-out, for all my Clojure development.
I've been using the Atom editor for about two years now.
Rich Hickey gave a very thought-provoking talk at Clojure/conj 2018 called Maybe Not, where he mused on optionality and how we represent the absence of a value.
One of the more mysterious new features in Clojure 1.
It has been a crazy busy year, both at work and personally, and it's hard for me to believe my last blog post was in April!Clojure/conj is coming up fast and the schedule was posted today, which has made me even more excited about it.
With the recent arrival of clj and tools.deps.alpha as a "standard" lightweight way to run Clojure programs and the seed for tooling based on deps.edn dependency files, it's time to take a look at the terminology used across Clojure's various tools.Running Java/JVM Programs
Sometimes you just can't help having a "random 3rd part JAR file" in your project.
I'm pleased to announce that the "Boot new" task formerly known as seancorfield/boot-new has moved to the Boot organization, as boot-clj/boot-new and that the group/artifact ID is now boot/new.You can use this to easily create a new Boot-based project:
A couple of years ago, I blogged about instrumenting Clojure for New Relic monitoring and we've generally been pretty happy with New Relic as a service overall.
Today I'm inspired by the latest issue of Eric Normand's Clojure Gazette which talks about why his "Joy of Programming" comes from learning and exploration.
Back in February I talked about boot-new and talked about a "future 1.
In my previous three blog posts about Boot -- Rebooting Clojure, Building On Boot, and Testing With Boot -- I looked at why World Singles decided to switch from Leiningen to Boot, as well discussing one of the missing pieces for us (testing).
