I see it differently. Consider a dev organization who is considering adopting Clojure as a supported (or even default) language. The case for such adoption is s

I see it differently. Consider a dev organization who is considering adopting Clojure as a supported (or even default) language. The case for such adoption is strengthened if you can make the argument that much of the shell scripting tasks can be done in the same* language and in a way that's more ergonomic and safer. That helps drive clojure adoption in a way that suggesting that instead dev teams adopting clojure should also learn scheme and write some of their code in that seems not nearly as compelling. It's the same reason that clojurescript is supportive of the overall clojure community, rather than being a distraction and diversion of resources. * It's not 100% the same, but for what's needed to replace bash scripts, it rounds to 100%.