The "level of productivity" when writing a browser app is going to depend completely on your other skills as a developer and not on the superficial differences between JS and Cljs. Only language zealots say Cljs gives them "whole new levels of productivity" over JS, learn to recognize them and ignore them.
For many, learning Clojure can make them better developers but most don't keep using it once they realized they can apply all the hindsights they learn from Clojure to a more productive ecosystem.
> For many, learning Clojure can make them better developers but most don't keep using it once they realized they can apply all the hindsights they learn from Clojure to a more productive ecosystem.
Exactly. I feel Clojure/Script too heavy to jump fully in, but it taught me about data structures, sequences, composition which lead me to Ramda.js.
This little functional library can be learnt in no time, and gives similar powers like Clojure, while learning Clojure and the ecosystem would take at least months.
If you have the chance to work with a team, you can get proficient in a couple of weeks. What you don't know right now is probably how the glue code for a cljs project works (eg shadow-cljs) and the core library.
For many, learning Clojure can make them better developers but most don't keep using it once they realized they can apply all the hindsights they learn from Clojure to a more productive ecosystem.