The author misses the third, most classical, and constantly useful option: doing it all yourself. Despite the scary name, there's not all that much to do, and this approach is the most widely supported in the community. The checklist is:
* SBCL/CCL (from your package manager or from official binaries),
* Quicklisp (by downloading it from https://quicklisp.org/),
* Emacs (in any preferred way),
* Slime/Sly (manually, or via `(ql:quickload quicklisp-slime-helper)`, or via using an Emacs distribution, such as Spacemacs with its common-lisp layer, which already contains preconfigured slime/sly).
There, you're good to go.
Using some sort of toolkit which enables interactive and incremental programming (such as Swank/Slynk on the Lisp side and any Slime/Sly client on the editor side) is an ABSOLUTE MUST while doing Lisp. If you're allergic to Emacs and therefore can't use Slime/Sly, use:
* slimv/vlime for vim,
* Alive for VSCode,
* Slyblime for Sublime,
* atom-slime for Atom.