michaelochurch's closing sentence: "Unlike the typical enterprise Java stack, it’s optimized for lifelong learners. That, above all, is why it will win." Here'

michaelochurch's closing sentence: "Unlike the typical enterprise Java stack, it’s optimized for lifelong learners. That, above all, is why it will win." Here's a speculative reason why it may not win: Java, Ruby, PHP, Python all won because intermediate level programmers could, all of a sudden, successfully build 2000-era sized apps. These languages are not doing so hot for 2013-era sized apps. It now takes extreme skills to successfully ship 2013-sized apps which is why a small portion of the programmers are making most of the money. The next language to win will be the one that lets an intermediate team ship apps again. Java let your average C++ programmer build much bigger apps without crashing. In 2000, Java forced you to program right by 2000 standards; the programmer needn't have figured it out himself. A language that lets a strong architect say, "NO! you CANNOT do I/O in the view, that goes in the controller!", that lets an architect shape what good code should look like and have the language enforce it, can lead a team of intermediate programmers to success. Clojure is like a musical instrument - a brilliant artist can do amazing things, but a mediocre artist will produce mediocre output. Clojure works great if you have 5 brilliant architects collaborating - Datomic, core.async, ClojureScript, all these are outputs of brilliant minds collaborating; the company behind these products has a reputation for only hiring the best of the best. But I think a business can make more money by putting 5 brilliant architects on 5 separate projects and giving them a bunch of intermediate programmers. The intermediate programmers learn; the architect multiplies; the pointy haired boss gets rich, everybody wins.