logoalt Hacker News

Steel Bank Common Lisp version 2.6.7

142 pointsby tmtvltoday at 5:11 PM48 commentsview on HN

Comments

taolsontoday at 9:03 PM

Fun fact I learned from a Func Prog podcast: the name Steel Bank is a play on it's origin as Carnegie-Mellon Common Lisp (Carnegie made his fortune in Steel, while Mellon did so with Banks):

https://www.sbcl.org/history.html

baqtoday at 6:45 PM

I wonder sometimes how the world would look like if lisp won and the unit of deployment was a lisp machine image, if that makes sense. How would a kubernetes optimized for lisp look like? How would AWS EC2 look like? etc.

show 8 replies
HexDecOctBintoday at 6:41 PM

If any SBCL dev is here, please add documentation for how to use the memory arena feature. The only doc is an very old proposal document.

show 1 reply
wk_endtoday at 6:02 PM

    * the SB-SIMD contrib now supports ARM64. (Thanks to Sylvia Harrington)
    * AVX512 instructions are now supported on X86-64. (Thanks to Robert Smith and Arthur Miller)
    * additional support for SIMD instructions on ARM64 and X86-64. (Thanks to Arthur Miller)
These seem like pretty awesome additions. Does anyone know how SIMD works in SBCL? Is this at the codegen layer? i.e. can it auto-vectorize or anything like that? Or are these intrinsics you have to explicitly ask for?
show 2 replies
WalterGRtoday at 6:50 PM

If memory serves, traditionally, CCL (Clozure Common Lisp [0]) had better support for Windows but SBCL was unbeatable for speed. Is that still the case?

[0] https://ccl.clozure.com/

show 1 reply
NeutralForesttoday at 6:15 PM

Great to see the project is still going strong, I kinda want to try CL but I always feel like I don't have a great use-case.

show 1 reply
sroericktoday at 6:31 PM

I'm going pretty deep on Lisp on accident - can anybody give me more context on this?

show 3 replies
arikrahmantoday at 5:39 PM

Great semver number