Half a year ago, after spending about a month learning haskell, I eventually switched to clojure because I had trouble actually making programs with it. I picked up the language quite quickly, largely thanks to that previous exposure to functional programming, but also because clojure for the brave and the true is awesome. After reading the first couple of chapters I jumped into my first project and reimplemented the ranking logic of a discord bot I had used more than a year prior for clash royale clan management. Then I wrote a dvd-animation with quil, a 2D graphics library. I even did my best to keep up with advent of code, doing the first week and documenting it via orgmode. Then things slowed down and after redqu, a reddit rss media scraper leveraging babashka, I only published some template repo and did some stuff on codewars I guess.
Then, last weekend, it hit me. It was something so obvious and important, yet obscured by my tunnel vision on functional programming: I'm primarily a sysadmin. The programs I write are short and achieve simple goals. They are used through the terminal and often use network connections. They run and then they exit. I'm not a "software developer", building large applications that run on some server for all eternity. Me being decent at coding is merely an accident, and should no longer stop me from growing the relevant skills for administration. This alone made me discard clojure as a viable language, but further problems with it quickly became obvious.
Another problem is clojures poor fitness for CLI applications. Parsing arguments... does not spark joy. Sure, it's doable and it's better than in many bad corporate languages of old, but it doesn't remotely compete with the default admin languages that I'll mention later. And forget about terminal user interfaces. There exists a gum wrapper for babashka, but at that point you might as well leave.
Now another domain I like to toy around with on occasion is 2D graphics. And quil is actually somewhat usable for that, and probably a really good library if you want to create generative art. But for games it's lackluster at best, because thanks to how clojure and functional programming works, managing state is a huge chore. This is hardly quils fault, but noteworthy enough for me to include it.
So since clojure is a hosted language that's hard to distribute, is mediocre at networking and cli apps as well as being not great at 2D graphics, I'm moving on. I'll miss my pipes, my higher order functions, multi-arity and the repl, but they are all sacrifices I'm willing to make to have a language that is actually good at the things I'm trying to do.
Well, first of all, I'll be shifting some focus away from programming to infrastructure administration. For that purpose I opened an account with digital ocean and started playing with ansible, which I plan on continuing. Some things I plan on setting up on that VPS through ansible:
In terms of programming languages: Shell, Go, Python, in that order.
Clojure is perhaps the best programming language out today in terms of good language design and power. But even with the best hammer I had to realize at some point that not everything is a nail. I'll keep you guys updated on further developments, especially once the VPS is set up with most of the things mentioned above.