4 ms·
Does your runtime still barf JVM stack traces? (attr.: http://www.loper-os.org/?p=42&cpage=2#comment-16767 http://www.loper-os.org/?p=42&cpage=2#comment-16767)
by rhabarba 10y ago
Does your runtime still barf JVM stack traces?
(attr.: http://www.loper-os.org/?p=42&cpage=2#comment-16767 http://www.loper-os.org/?p=42&cpage=2#comment-16767)
Leaving this aside (after all, it might or might not be a matter of taste), it totally is. The Common Lisp ecosystem is pretty well alive, despite of the rise of Racket and Clojure. You should really give it a try one day. :-)
- nextos 10y agoCommon Lisp was the first Lisp I tried. But I found the library ecosystem a bit disappointing. This was more than a decade ago, though. No idea if Quicklisp has made everything more lively. Clojure is nice. I like the emphasis on functional programming, and a very clean set of basic data structures and operations on them. Plus lots of great libraries. Nonetheless, being on the JVM seems both a blessing and a curse. And I would love if it was a lot more performant. Clasp is tempting: https://drmeister.wordpress.com/2015/11/23/why-common-lisp-for-scientific-programming/ https://drmeister.wordpress.com/2015/11/23/why-common-lisp-f.... I wish concurrency was better.
- rhabarba 10y agoClasp seems to be much slower than SBCL (yet?). But yes, the amount of libraries has surely grown over the past few years, probably even too much: http://eudoxia.me/article/common-lisp-sotu-2015 http://eudoxia.me/article/common-lisp-sotu-2015