Slightly tangential, but I wish some Lisp would make a serious comeback and challenge mainstream languages. For this purpose, libraries are essential. So better tooling would help, and that's why Ultralisp and Quicklisp are interesting.<p>Clojure is very nice. I have used it for several projects. But sometimes I would prefer not to rely on Java libraries so much, and cleaner stack traces.<p>Racket may get some critical momentum now, with the whole merge with Chez.<p>I don't have high hopes for a Common Lisp implementation, as the ecosystem has become too fragmented and stagnant. But I wish I could be surprised here. Shen introduced some great ideas to make a powerful static typing an option in Lisp [1].<p>[1] <a href="http://www.shenlanguage.org/" rel="nofollow">http://www.shenlanguage.org/</a>
I'm not sure this is a great idea.<p>I have a couple projects in QuickLisp, and more than once I've broken them after I pushed incremental or non-working changes to my repo, didn't go back and fix them in time, and QL pulled the broken code.<p>Developing in branches would solve the problem, but not everybody does that on smaller informal projects.<p>On the other hand, I've also been annoyed waiting for bug fixes to trickle through to Quicklisp, so it's not an entirely bad idea...
Url changed from <a href="https://github.com/ultralisp/ultralisp" rel="nofollow">https://github.com/ultralisp/ultralisp</a> to the project page.