3 ms·

I'm not sure when your last exposure to the ClojureScript ecosystem was, but almost nothing you mention is a problem as of 2016: debugging, hot reloading, large

I'm not sure when your last exposure to the ClojureScript ecosystem was, but almost nothing you mention is a problem as of 2016: debugging, hot reloading, large JS deps, etc. I'm biased, but I think ClojureScript is the best way to use the JavaScript platform today. Awesome core library, consistent build process, best of breed tooling, persistent data structures, flexible syntax (JSX is madness compared to hiccups); I could go on. JavaScript the platform may have it's warts, but ClojureScript is all beauty :)

bootload 10y ago
"I'm biased, but I think ClojureScript is the best way to use the JavaScript platform today. ... JavaScript the platform may have it's warts, but ClojureScript is all beauty :)" I've been slow to this, but yes this summarises why this particular language is good to use as a better JavaScript.
shadowmint 10y ago
Got a link with specifics? I've never seen breakpoints & source maps working properly; just a series of blog posts by various people who've tried and failed to get it working.
- iLemming 10y ago
  That's like 2 years ago. Source maps work fairly well today.
  - shadowmint 10y ago
    come on, dont just wave your hands in the air and say its all good. how do you do it then?
    - iLemming 10y ago
      What do you mean how? Clojurescript compiler today has four different, well documented options related to source maps: https://github.com/clojure/clojurescript/wiki/Compiler-Options#source-map-timestamp https://github.com/clojure/clojurescript/wiki/Compiler-Optio... Just yesterday I placed `(js* "debugger;")` in my .cljs code and it stopped exactly where I wanted it. And showed exact piece of Clojurescript (not compiled JS)