I think most are related to easiness, and so not recognized as an advantage by many Clojure acolytes (see: Rich Hickey&#x27;s Simple Made Easy talk).  Others are a consequence of shared state; also not recognized as a positive in Clojureland (rightfully so in most cases).<p>Here&#x27;s my list:<p>- Database migrations<p>- Fast TDD (for some sub-Gary Bernhardt definition of fast) with access to the app environment.<p>- content negotiation<p>- Authentication with Devise and Omniauth<p>- Easy built-in support for caching<p>- Easy built-in support for background queue systems<p>- Easy support for one-off or occasional scripts with access to the whole app environment (rake tasks)<p>- Pry (yes, Clojure has awesome REPL powers, but Pry is so easy to use, and you have access to the whole app environment (no loading &#x2F; switching namespaces or abuse of user.clj))<p>There&#x27;s probably some solution to each of these.  But all require you to find&#x2F;know the options, and be able to evaluate which is best for you (&quot;all REAL devs . . .&quot; sure, sure).  For Rails, all of these are available to you in the Rails Guides, except for Devise+Omniauth, which has an extensive wiki and tons of StackOverflow answers.