I'd imagine this would apply to just about any other language as well really. The Ruby community really is fortunate to have such brilliant free resources out there for learning Rails and the language.
Clojure to me seems like a language culture that would likely tend towards smaller libraries that do specific things than something with batteries included and such like Rails.
If you want something on the JVM with more of a batteries included approach Play Framework for Java and Scala is pretty nice and Lift for Scala is cool if you're willing to take a very different approach to your web stack.
I decided upon Clojure as I think it meets the needs of my project well, which is basically an expert system. I need to consume a number of domain specific java libraries, and the native support for logic programming with core.logic and datalog is a big win. Clojure certainly wasn't the easiest choice - I would be much further ahead if I started with Ruby.
> Clojure to me seems like a language culture that would likely tend towards smaller libraries that do specific things than something with batteries included and such like Rails.
I should clarify that I think Clojure's favouring of smaller composable libraries is ultimately a better approach than the monolithic framework. It is much more difficult to get to a point where you're productive however.
Initially there was going to be a complimentary framework for Noir called Pinot for client-side code (clojurescript), which has since been broken up into a number of different libraries. Having more guidance around structuring large projects with these new tools (https://github.com/ibdknox/fetch, https://github.com/ibdknox/crate, https://github.com/ibdknox/jayq) in the context of a Noir app would be superb.
I suspect these things will come given time - web development in Clojure is evolving very quickly and compared to Ruby is relatively new. The Clojure community is also much smaller than the Ruby community I would imagine, so it follows that there will be fewer learning resources about.
But with rails as soon as I wanted to do something less than extremely typical I was in a world of terror an ambiguity. It was so hard to figure out the "right" way to accomplish a lot of tasks.
I remember I once suggested that the people behind GitHub consider whether they could leverage their pull requests as a practical alternative to Stack Overflow, but they basically told me (in a formal boilerplate response) to fuck off.
1: Study it
2: When you're lost, research and ask someone
I learnt Ruby kind-of-alongside Rails and wish I'd spent more time focusing on the language itself; I'm going back and deepening my knowledge of it now. But it depends on how your mind works, whether you want to get a Rails project going yesterday, what knowledge you have locked away somewhere, and so on.
I've put in a bit of time in Ruby and it's opened up Rails (and programming in general) for me more than I thought it would. The biggest advantage, besides just general programming, is reading other people's code and documentation. Recently, I've been exploring i18n (internationalization) in Rails. By going into time_ago_in_words helper, I was led to the distance_of_time_in_words helper and it's source code (https://github.com/rails/rails/blob/bd8a9701c27b4261e9d8dd84...). By understanding enough ruby, the Rails code became a wonderful source of documentation.
Which is a great first tutorial to get some basic with Rails.