Clojure Text Editors
I'd been a professional software developer for a number of years before I came to Clojure. So, it's fair to say that by the time I went all-in on Clojure I had, thankfully, seen some things and started to form opinions around what I felt was the "best" way to practice software development.
One of the tenets of my model? I should always be capable of growth. To me, this means accepting the opportunity to revisit and refine my opinions and beliefs. One great way to do this as a programmer is to be "new" at something again. For example, learn a different programming language. Clojure was that language. I chose it because it would expose me to new ideas like functional programming, lisp etc.
With the language chosen, I just needed to start coding Clojure. At the time, my mindset was total assimilation: I would think as they do and use the same tools as them. This meant emacs because all my research and conversations up until this point with other Clojurists led me to the opinion that
emacs was the tool for a Clojure developer.
Turns out that for me, choosing emacs was not a great choice (more on that later) and I should have stuck with the editor I knew best. This would have allowed me to spend more time focusing on Clojure.
This is how it goes though. These are the lessons. It's with this in mind that I will hopefully help the next person interested in Clojure, aspiring or experienced, by walking through some of the Text Editors of Clojure.
The rest of this article will be bikeshed city. The hope? By documenting the thoughts and providing a few words of encouragement we can save some future Clojure developer some time. With that, this post will cover the following topics:
Let's start by introducing the top Text Editors for Clojure(Script) development by usage:
There is nothing special about the above list. Yet, where it starts to feel prohibitive is the idea that you have to use one of the first 3 Text Editors in order to be productive in Clojure. So, if you read no further, take this with you: you don't need to use Emacs, IntelliJ or Vim to learn or be good at Clojure.
This leads to the next part: which editor should you use? To answer that, try to answer the following questions:
- Are you an experienced developer through hobby or profession?
- Are you new to the programming game?
If your answered yes to the first question, the choice is simple: Stick with the editor you're comfortable with!
If you answered yes to the second question, my recommendation is to choose
VS Code. Read on to find out why!
A Text Editor is one of a developer's primary tools because we spend most of our work life inside of it. Given the time we work with our Text Editors, there is something to be said for the satisfaction we derive from using it.
Over time, this satisfaction grows and we begin to associate the qualities of the developer with the editor itself. It becomes a zero sum game.
There are some obvious problems with this mentality and it begins with the fact that tools are tools. They either help us be productive, or they don't. Further, the productivity one human gains from a tool, the satisfaction as we called it earlier, is likely going to be different from the next person. You do you.
Knowing this, let's put the cards on the table and review the qualities that allow me to feel satisfied with the Text Editor I choose. I alluded to this earlier, but for me it's mainly how productive I can be in my tool of choice. How I define productivity is by the
startup cost and
utility of the editor itself. What do each of these mean to me?
Startup cost is about whether or not I can use the editor regardless of my operating system and how much configuration I need to get it going on a new development environment.
Utlity is performance and customizability of the Editor. For performance, I mean that when I do things like search, open large files or use plugins the editor does not eat all of my system resources and grind to a halt. This would be intrusive to my workflow. When it comes to customization, I like it when I can configure my editor easily with languages and tool chains I already know.
As you may have gathered, my definition of satisfaction has led me to prefer a spartan editor environment. Yet, this is not always how I felt. I only realized this was how I liked to work when I saw truly productive developers operate in environments devoid of frills.
All of this is to say that this is my preference. This preference is one I have built through years of experimentation and questioning my workflow. If you have been developing for a while, you will also go through this learning process. This is a beautiful part of the journey because it really is about you, your likes and dislikes and how far you want to go.
And now we're back to the original question about which editor you should use. I said earlier that if you're experience, go with the editor you already know. If you are a new programmer and don't have deep roots with any particular editor, choose
My rationale? All of these editors are easy to use, work on all operating systems, have active and easy to access communities and support all the modern Clojure tooling one could ever want. But there is also a more significant reason. I have learned that when learning something you should focus on learning that one thing.
Choosing editors like Emacs, Vim, or Intellij mean you are going to spend more time learning and configuring the editors than programming. It's going to get in the way of the learning journey. So do yourself a favour and focus on learning Clojure. You can always try the other editors when you develop some sensibilities around the workflow you want to pursue. But that is more of an optimization strategy than a tactic which will enable you to improve the learning process.
Knowing this, lets move onto how I setup Atom for my development workflow.
Atom is currently my preferred text editor for Clojure development. The reason? it's portable, easy to setup and customize.
Below you will find an outline of how I setup Atom for Clojure development. I have also released a Clojure Text Editors Youtube series where I walk you through how to setup Atom for Clojure development from scratch.
I have always found that to be productive with Clojure you don't need many tools. This is great because it means I can keep a relatively spartan setup for my Text Editor. Now, let's take a look at the plugins I use and how I configure them.
- Description: Chlorine depends on this.
- Configuration: None required.
- Description: Integrate your Clojure REPL into your editor.
- Configuration: Add the Chlorine hotkeys. Here is an example of where to put them.
- Description: Automatically balance your parens. Translation? Thinks less about your parens.
- Configuration: The default settings are great, but I recommend enabling
Remember that no matter what language you choose, there are going to be a ton of micro decisions to make. The important thing in the beginning is to focus on the language and the learning process and not stress over the tooling. Be good to yourself in your learning journey and try not to obsess over all the details or aligning to the ideal programmer stereotype.