YOyogthos·Sep 8, 2015
The first issue is addressed by templates. I maintain Reagent and Luminus templates and make sure that Cljs compiles correctly for both dev and prod targets.
While I understand author's complaint regarding it being difficult to retrofit the template code into an existing project, I really don't see a simple solution to that.
Standard behaviors can be extracted into plugins and libraries, but project specific configuration really does have to be part of the project.
The Figwheel REPL can be trivially connected to an IDE as seen [here](http://www.luminusweb.net/docs/clojurescript.md#clojurescrip...). This should work with any editor the has nREPL support.
There's really no good reason to use the built in REPL on the command line when you can connect the editor and send the code for evaluation directly from there.
In terms of client-server i
Read the rest
nteraction I found that using cljs-ajax https://github.com/JulianBirch/cljs-ajax on the client coupled with compojure-api https://github.com/metosin/compojure-api on the backend works really well.
With regards to Vim, it's definitely not as popular as Emacs or Cursive for Clojure development, so it's not surprising that the tooling around it would be more spotty.
I think this is one area where Clojure shines overall though, as there is support for it in majors IDEs and many popular editors. However, using something that's popular with the community will obviously get you the best mileage.
Overall, I still find ClojureScript to be far more productive than anything I've used to develop on the front-end.