[1] http://blog.cognitect.com/blog/2015/6/30/walmart-runs-clojur...
Off the top of my head:
Naughty Dog's games (Crash Bandicoot, Jak and Daxter, Uncharted) are powered by their own Lisp implementations. Google for "GOOL" and "GOAL".
Grammarly uses Common Lisp.
Oh, and if you're searching for air travel connections, your query most likely goes through a huge Common Lisp system (search for ITA Software).
[1] https://github.com/nexe/nexe
They also mention static binaries which Node does not solve.
Agreed it doesn't help with static dependencies, which is why I didn't mention it ;)
Many of us who actually run Clojure in production have been bit by this, and Clojurescript has been fast enough to alleviate the issue. Not a straw man, a community meme.
[1] https://github.com/zeit/pkg
I like the fact that they are a practical company, using Go when needed where "static dependency compilation and fast start-up are more important". I wonder if the ClojureScript's annoucement on integration of NodeJS modules [2] changes that? Also, Lumo [3] is definitely a move in the right direction for this, addressing the slow start-up times for Clojure/ClojureScript, making it suitable for shell scripts and CLI binaries.
> Having a lingua franca also helps reduce overhead when engineers want to move between layers of the stack.
The way I see it, Clojure allows you to use a single language and syntax from the super heavy backend stuffs, to the front end and now to small, fast CLI tools and scripts. A candidate for the "Business English" of the technical world as it were.
[1] http://www.paulgraham.com/avg.html
[2] https://news.ycombinator.com/item?id=14754614
[3] https://github.com/anmonteiro/lumo