“Using the REPL” actually means typing your code in your favorite editor. However, one sends the code to evaluate in a REPL, which may not even be visible at all. Once the code is evaluated, the results immediately show up in the editor, so you get the feedback right away. Obviously, this requires some upfront setup, but a proper Clojure REPL setup exists in all major editors. Just google it.
Note that one normally sends the code to evaluate with a single key stroke. Note also, a very important point that people often miss, is that this “sending code to evaluate” is uniquely convenient in Lisp because of the parentheses.
There’s a notion of “form” in Lisp, that is the code enclosed between a pair of parentheses, which can be independently evaluated. So, when next time someone insists that their favorite non-Lisp language also has a REPL, ask them, does it have a notion of “form”?
The benefit of a form, is that one no longer needs to use a mouse or some awkward key combinations to painstakingly select a region of code first, before sending it out for evaluation. Instead, one can use a single key stroke that means “evaluate the form under the cursor”, or “evaluate the form before the cursor”, etc, to precisely define the scope and send the code at the same time. — How much can a Clojure developer do alone?

Successful Lisp: How to Understand and Use Common Lisp. #lisp

I mostly don’t care how popular Lisp is. I am not using Lisp in order to score better in a popularity contest. I am using Lisp because it is the best programming language I know for the kind of programs I write. I don’t think there is anything particularly or seriously wrong with Lisp. It might be that at the moment it does not provide what some people have come to expect from a programming language (free cross-platform implementation with all the libraries you could possibly want). Whether this will ever happen, I don’t know, and I don’t care (though I respect that others might). I do think I know that some of the people who want this to happen will have to get their hands dirty and just do it. No amount of lamenting is going to magically create any libraries. — What is wrong with Lisp?

First contrib for a very useful Vim plugin ;-)

As I write this, I realized that this PR has already been merged.

  London Grammar, If You Wait.

I updated my Zsh config today, just to make terminal tabs (in Kitty) show the current running process, instead of the default $SHELL. Looks much nicer!

TL;DR Add this to your .zshrc or wherever you put custom settings:

preexec() {
    # See, e.g., https://www.davidpashley.com/articles/xterm-titles-with-bash/
    print -Pn "\e]0;$1\a"
    # or, equivalently,
    # printf "\x1b]0;%s\x07" "$1";
}

precmd() {
    # Clean up terminal title (in case Neovim doesn't restore it to its initial state)
    # printf "\033]0;\a"
    # or print relevant stuff
    # (%~ current working directory; %1~ directory name only)
    print -Pn "\e]0;%1~\a"
}

I’m delighted to start using Julia again. The 1.6 milestone, which may eventually becomes the next LTS version, looks much more stabilized than the previous versions I quickly tested in the past (1.0, and 0.3 to 0.5 beforehand). And, they got a true graphical engine. #julia

The success of Julia in the scientific-computing sphere is an important development at the intersection of science, engineering, and free software (in the free speech sense). Until the advent of Julia, the only programming language with comparable influence and ubiquity in the science world was Fortran. — Julia 1.6 addresses latency issues

At last, a tool to cleanup the mess in your $HOME/.stack directory. Just went down to 3.9 Go instead of 9.1 Go.

A Map of the Internet 2021.