My current CLJS setup is boot with boot-cljs, boot-reload and boot-cljs-repl. They're configured using normal Clojure code in a build.boot file and the entry points are configured in live-reloadable *.edn files.
That setup is simpler and far more powerful than anything else I've seen in other languages.
I was using leiningen previously but boot proved to be more powerful for less work in my case.
https://github.com/boot-clj/boot
https://github.com/boot-clj/boot-cljs
I maintain Luminus http://www.luminusweb.net/docs specifically to make it easier for people to get started. For example, if you wanted to make a new web app with Clojure you could do:
lein new luminus myapp
cd myapp
lein run
That's all there is to it.I would recommend using Leiningen, just because it is more popular. If you're starting out, then you don't really need to change that much stuff in the project file aside from adding dependencies.
And thank you for your work in the community. Luminus is great, and I Macchiato looks really nice as well.
As I pointed out in the original comment, you don't really have to use Cursive if you're starting out. Cursive is great for working on serious projects, but it's certainly not a requirement for trying Clojure.
Aside from Atom, you also have Light Table, VS Code, Vim, Emacs, and Eclipse. Chances are a lot of people would be using at least one of these tools. As far as having to download the JVM and Leiningen, it's not really different than what you'd have to do for Python, Ruby, or Node.js.
So, I don't think the situation for Clojure is really any worse than most languages. That said, I think that Nightcoders could remove any friction in starting with the language.
boot-reload will hot reload new code on file changes, and optionally run a client-side hook. I use it to remount my react views. boot-cljs-repl provides a REPL into the browser you can use from the cmd line or directly in your editor. I'm using it with emacs-cider, but there are clients for most major editors.
Usually there's one place for dependencies, one for builds, one for configuration; each using their own tools and/or languages. That list grows quickly as well. A single tool to drive it all is bliss.
I recently had to take over a few Ruby projects and the tooling is so spread over its hell; bundle, gem, rake and others.