Outdated article post-LLMs, if you are still taking to heart what this article says you are working against the trend.
You don't need any inner working of clojure or any lower language for that matter. It's all available within your reach. Don't let the people who have built an identity over the tools that they have chosen, they can't give you any meaningful advice anymore with what we have as tools.
I'm saying this as someone who has worked with clojure for over a decade. There is no point in gate keeping things anymore. It also means that the point of clojure which is supposed to have a lot of DX built into it , is gone with LLMs.
Software is largely solved now and the only thing that matters now is distribution so start thinking about your product and how to market it.
By a weird stroke of luck, clojure was one of the first languages I learned. And yeah, I guess it left a lasting impact on me in the form of an appreciation for immutability and dataflow programming.
Unfortunately it also left me with an extremely deep distaste for dynamic types, and in particular, the blind usage of lists and maps for everything. The ML family of languages finally gave me a paradigm worth keeping around.
I started learning Clojure when I was 17, but then later moved away from programming. It's done the opposite with me, I struggle to really get the benefit of static types and I still think of everything as maps and functions.
There was a time in university where I started my days with doing some 4clojure puzzles. I became so obsessed, I managed to solve almost all of them. It's wild what an impact these few weeks had on my programming abilities. It's a beautifully designed language that makes you think in data structures and their transformations.
As a side note: I code Clojure in Lightroom. It was so cool to see your code instantly evaluate and trace through your functions.
You don't need any inner working of clojure or any lower language for that matter. It's all available within your reach. Don't let the people who have built an identity over the tools that they have chosen, they can't give you any meaningful advice anymore with what we have as tools.
I'm saying this as someone who has worked with clojure for over a decade. There is no point in gate keeping things anymore. It also means that the point of clojure which is supposed to have a lot of DX built into it , is gone with LLMs.
Software is largely solved now and the only thing that matters now is distribution so start thinking about your product and how to market it.
Unfortunately it also left me with an extremely deep distaste for dynamic types, and in particular, the blind usage of lists and maps for everything. The ML family of languages finally gave me a paradigm worth keeping around.
As a side note: I code Clojure in Lightroom. It was so cool to see your code instantly evaluate and trace through your functions.
https://github.com/conductor-oss/clojure-sdk