Clojure is frustrating... and it is a good thing
There are two very good reason for taking as much time as necessary to make any design really good, both in Clojure itself and in the core libraries that are likely to be embraced as a part of the language.
The second reason is that discovering a simple Simple Made Easy solution to a problem takes a lot of time, thinking, and experimentation. Stu Halloway explains that convincingly in Radical Simplicity. You cannot really rush it.
So yes, the slow speed of design changes to Clojure is very frustrating when you wait for the outcome. But given the outmost importance of true simplicity and the longevity of the result, the benefits far outweigh the cost.
Are you benefitting from my writing? Consider buying me a coffee or supporting my work via GitHub Sponsors. Thank you! You can also book me for a mentoring / pair-programming session via Codementor or (cheaper) email.