re-frame-template

I'm glad that my comment gave you some motivation. CLJS also had a steep learning curve for me. There are a thousand different aspects to learn, but just start with a template or example app and try to understand everything step by step. Maybe the re-frame template (https://github.com/Day8/re-frame-template) will give you a good framework for building your first webapp. And if you get stuck, just visit http://clojurians.net/ - very helpful community. Good luck!

If you want it to feel more like backend development, give clojurescript a whirl. Best way to do that is start with this template: https://github.com/Day8/re-frame-template Which is based on this library: https://github.com/Day8/re-frame ClojureScript is fantastic. Being immutable as a baseline makes it work so much better in the React world of things. That said, if you haven't used any Lisps it can be a bit intimidating (for me it still is, a bit), but you get to the point fairly quickly where things can be both daunting and productive at the same time. If you prefer to stick with more raw JS, I recommend React without a data-framework until you find you need one. Raw react components are plenty to get you started.

This: git clone https://github.com/Day8/re-frame-template lein new re-frame <project-name> lein figwheel Program with a great functional language (Clojure) and watch magic happen when Figwheel dynamically reloads all of your changes in your browser...

I've used clojurescript commercially for a couple of years. It has been a good experience. More than anything it has completely changed my world view (and I'm a very experienced, older programmer who has seen a bit). I feel very lucky to have had this opportunity. IMO, some of the issues you raise are genuine, some not. For example, the JVM startup time issue is never, ever a problem. If it is, you aren't using the tools right. I use Cursive and figwheel etc, so I find the tooling generally fine and in many ways excellent. The trajectory in this area is good. Debugging initially can be rough. Knowing about things like cljs-devtools can dramatically improve things. But, yeah, valid point. And, yes, poor error messages can definitely be a problem initially -- although this has improved over the last year. To get going, I'd recommend you u

I've been using reagent with re-frame[1]. Routing just uses goog.events and goog.history to listen for navigation events, secretary[1] to define routes, which update the state rendered by your components. The code is here: https://github.com/Day8/re-frame-template/blob/master/src/le... [1] https://github.com/Day8/re-frame and https://github.com/Day8/re-frame-template You'll have to do `lein new re-frame <project> +routes` to pull in the routing template. [2] https://github.com/gf3/secretary

And for anyone who'd like to jump right in: https://github.com/Day8/re-frame-template Includes Figwheel, and (optionally) Secretary.