If you bring Clojure to a work environment, be gracious and go slowly. The truth will not bring you laurels. When you land in your alien spaceship, and they're

If you bring Clojure to a work environment, be gracious and go slowly. The truth will not bring you laurels. When you land in your alien spaceship, and they're all riding horse and cart, they're more likely to stone you than hail you a saviour. Recently I experienced this by proposing a talk at a conference for a more popular Object Oriented language. The talk was on using functional techniques and Phil Bagwell's persistent data structures to improve programming in that language. I got strong rejections from every reviewer and some comments that made me realise that some people may feel threatened by this "new kid on the block". This is OK. It's not for everyone. Some programmers are never going to try it, as a matter of principal! Seek out those excited by the language, and work with them. I've had success introducing it, both in and out of work, by going slowly and carefully, finding those developers who are interested and using it with them, and introducing it where it fits the best and solves a big problem more elegantly. Keep coding in Clojure. It's a beautiful thing.