Since you have all been so kind, I wrote a new article about Clojure CLI tools aliases and why they deserve a little design thinking. https://practicalli.github.io/blog/posts/clojure-cli-aliases-deserve-designing-too/ I hope you find it useful background as to one reason I created the practicalli/clojure-deps-edn GitHub repository. Thank you.
I am also working on an article discussing the merits of running a repl external to an editor and connecting, verses running the repl from the editor (jack-in). This is only a draft at the moment, but feedback is welcome... hopefully should be finished by the weekend https://practicalli.github.io/test-blog/posts/clojure-repl-jack-in-or-connect/
Was interested in this: 404 ERROR ! PAGE NOT FOUND
I guess it just graduated from the test blog. I'll look in the regular blog.
Its back. https://practicalli.github.io/test-blog/posts/clojure-repl-jack-in-or-connect/ I am sharing a test and staging environment on the same github pages (I should fix this) I've been working at some other content for the last couple of days, but should get back to this on Friday.1
Interesting. After a bunch of dabbling in Clojure I’m trying to grok more of it. The jack-in thing... yeah. One question I wanted to figure out for myself is if I should get used to having several repls running - one per project and one extra as a “scratch” repl for testing random stuff. I’ll read up... 👍😀
I've never used a separate scratch repl, but I do have a separate repl for each project. Sometimes I will have multiple repls running which isn't usually a problem. Things to avoid with multiple repls includes: using the same network port or similar shared OS resources. I will close down other repls if the project I'm working on will use lots of data or I want to do some very specific bench marking.
For testing random things I use a rich comment block (or just commented code) or if there is a lot of experimenting, then I create a separate namespace called design-journal.