Yes, I was responding mostly to the grandparent's move towards discussing this sort of tradeoff in the commercial space, not just in the open source space. To s

Yes, I was responding mostly to the grandparent's move towards discussing this sort of tradeoff in the commercial space, not just in the open source space. To stick with open source, it could become the case that moving away from Clojure leads to a cooling of contributors, existing or new. If you're looking for an Apache project to start contributing to, there's no shortage of Java projects. But if you like Clojure or want to learn it better, hey look there used to be this Clojure one, cool. If you liked the Storm project specifically and wanted to conribute, I don't think the language would get in the way that much. (Speaking personally if I had more time and energy I'd like to try and contribute to the Godot project despite my desire to never have to program in C++ again. It's a sufficiently cool project to overcome that.) Optimizing for new volunteer contributors goes beyond core language choice anyway. For an interesting description of how the game Battle for Wesnoth tried to do it, see: http://aosabook.org/en/wesnoth.html http://aosabook.org/en/wesnoth.html