CircleCI uses it - it's great. The upsides are: - the great concurrency model - the REPL - being able to edit with Paredit, - it's a great language - It's

CircleCI uses it - it's great. The upsides are: - the great concurrency model - the REPL - being able to edit with Paredit, - it's a great language - It's also amazing for hiring devs: there is a niche pool of devs who want to use clojure, and it's easy to hire them since demand for them is low. (Vs the thousands of Rails companies who are competing for a much larger pool) - being able to use clojurescript, in particular using Om (we use a pattern which is similar to the Elm Architecture, and it's great for writing frontends with). The downsides are: - mostly related to Java. Startup time is shitty (which is why you use the REPL a lot). - Libraries are often unmaintained (though often it doesn't matter, since they are typically very composable and don't need changing). - The web framework story is poor too - it's not nearly as advanced as the rails and nodejs worlds - you have to compose different libraries which is sometimes good and sometimes bad. - Finally, Rails encourages good web-app best practices: you can only really scale Rails horizontally, so you start with queues and horizontal scaling and workers. With Clojure, it's tempting to run things in threads and pools since it's so easy to do. But it scales poorly, and leads to concurrency bugs you wouldn't get in the Rails world.