The whole point of the comment was that Clojure, by and large, forces you to work one way and Python doesn't. The point of my comment is that it's not true (ex

The whole point of the comment was that Clojure, by and large, forces you to work one way and Python doesn't. The point of my comment is that it's not true (except in a narrow educational meaning). Your working environment (managers, colleagues, existing codebase) is what defines your limits in general, including language, approach, style, and frameworks. If your current shop can't accept your call to write more functional code in whatever language is used there, it obviously won't start developing in Clojure. It works exactly this way, not in the opposite direction. Ergo, the guy's problem was that his environment wasn't inclined to switch from OO. He couldn't say "Mates, let's use Clojure, because it will finally FORCE you to discover the beautiful world of FP", because they just want to keep doing what they were doing yesterday. Fixed that for you. It's not a correction, and I hope you see now what I mean.