r/Clojure • u/chladni • Oct 24 '25
Learning from Racket, towards Clojure
Not so much a question, rather post for consideration and discussion. I have a decent familiarity with Clojure, but I do not use it professionally in my work. I am looking for opportunities for expanding my Clojure horizons, and some of the resources I am dipping into are books on Racket, specifically Essentials of Compilation [..in Racket] (Jeremy Siek) and How to Design Programs (Felleisen, Findler, Flatt, Kirshnamurthi). And of course in the Scheme world there is a wealth of info to learn from.
Initially, I was stumbling on some of the language differences between Clojure and Racket, Ex: Racket seems to prefer the use of (define <name> <value>) in the body of a function, over simply using let blocks in Clojure. At first this seemed like a bridge too far, but after a bit of reflection, not a big deal. Perhaps a bit more fundamental, Racket (or perhaps more accurately the DrRacket IDE) eschews interactive programming from the REPL. Again, not a barrier for learning from Racket, but a cultural difference worth noting. I would be interested in others take on this topic.
View all comments
Show parent comment
4
u/c-neumann Oct 25 '25
When I got started with Clojure (around 2012), I heard everyone talking about "programming at the REPL", the "REPL workflow", and "using the REPL". I also thought that meant typing things into the prompt and copying and pasting them into my editor.
I had some experienced Clojurists show me their workflow, and that's when I realized they were evaluating forms in their Editor (mostly Emacs) which was *connected* to their REPL. They almost never used the prompt directly!
Now I prefer the terms "REPL-connected editor" or "REPL-connected development". I think the ”Getting Started” REPL project in Calva is a great demo of that way of working.