If you want to get started quickly and don't want to stress about how to do something than Elm. From my personal subjectiv experience I never felt such joy to build a web-based frontend. Because of its type system and the model it enforces on how to do things. Also in my experience when the code compiled it really just worked (besides logic errors the compiler can't catch). Refactoring was also a breeze with the help of the compiler. Another big plus are the error messages procuded by the compiler which are the best i've seen so far. So overall i found it to be a really good beginner experience.
Whereas CLJS is at the other end. A tool for experienced developers who know what they want and how to do it. As it requires you to make a lot of choices. That Elm, for most parts, already made for you.
The Smalltalk world also provides such tooling. Which offers a lot more flexibility on how to visualize source code. Unfortunately though it requires quite some effort to learn and use. But once you got the hang of it it's pretty awesome to browse source code and discover it's overall structure. And it allows you to ask more specific questions about the code and visualize the results as you see fit. Which can help a lot in actually finding not so good abstractions and architectural decisions.
Ansible for dev boxes or smaller deployments.
For large-scale deployments CFEngine3. When deployed within a cloud environment one doesn't even need a master node for CFE3 but the agents can just pull the latest config state from some object storage.
Whereas CLJS is at the other end. A tool for experienced developers who know what they want and how to do it. As it requires you to make a lot of choices. That Elm, for most parts, already made for you.