<story><title>SBCL: New in Version 2.1.0</title><url>http://www.sbcl.org/all-news.html#2.1.0</url></story><parent_chain><item><author>gautamcgoel</author><text>Anyone here use SBCL or Common Lisp? Curious what you guys think of it.</text></item></parent_chain><comment><author>heisig</author><text>I use Common Lisp for most of my daily programming, and SBCL is a big reason why.  Once you get over the initial hassle (getting used to the Emacs+SLIME tool chain and learning to read the compiler diagnostics) it really gives you the productivity of Python with the performance of C++.  And a lot of that performance is thanks to the tireless effort of the SBCL developers, who have been churning out a new release every few months for the last decades.&lt;p&gt;Kudos to all SBCL contributors!</text></comment>
<story><title>SBCL: New in Version 2.1.0</title><url>http://www.sbcl.org/all-news.html#2.1.0</url></story><parent_chain><item><author>gautamcgoel</author><text>Anyone here use SBCL or Common Lisp? Curious what you guys think of it.</text></item></parent_chain><comment><author>lisper</author><text>Yes, I use it professionally, and have for over 30 years, since before it became Common Lisp.  It is far and away my favorite programming language (hence my HN handle :-) for two reasons: macros allow me to capture any design pattern and seamlessly add it to the language as a programming construct, and the generic function model of OO built in to CL is vastly more powerful than the C-based single-dispatch object.method() model that is ubiquitous in the rest of the programming language world.</text></comment>