I never did see his definition of "win", but Clojure does have a great community and I consider that one of its greatest strengths.
That said, I can never see Clojure "winning" as in how Java "won". For all of Clojure's strengths, it's at best an intermediate step up from Ruby, Python, Perl... It's not that next order of magnitude leap of productivity that is necessary to "win".
The research just isn't going in that direction. The research is going into type systems and static guarantees. And I think the real productivity boosters of the future will be in very smart tooling - a conversation with your IDE I would say. Maybe Clojure could have different views (different surface syntaxes). Maybe it could be the basis of something like intentional programming. But straight Clojure with Emacs isn't going to be "winning" in the big way.
That said, I can never see Clojure "winning" as in how Java "won". For all of Clojure's strengths, it's at best an intermediate step up from Ruby, Python, Perl... It's not that next order of magnitude leap of productivity that is necessary to "win".
The research just isn't going in that direction. The research is going into type systems and static guarantees. And I think the real productivity boosters of the future will be in very smart tooling - a conversation with your IDE I would say. Maybe Clojure could have different views (different surface syntaxes). Maybe it could be the basis of something like intentional programming. But straight Clojure with Emacs isn't going to be "winning" in the big way.