--- title: Steel Bank Common Lisp version 2.6.7 | daily.dev description: Release notes covering multiple recent versions of Steel Bank Common Lisp (SBCL), from version 2.5.3 through 2.6.7. Highlights include a new SB-MANUAL contrib... canonical: https://daily.dev/posts/steel-bank-common-lisp-version-2-6-7-qsnxliuey twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Steel Bank Common Lisp version 2.6.7 | daily.dev og:description: Release notes covering multiple recent versions of Steel Bank Common Lisp (SBCL), from version 2.5.3 through 2.6.7. Highlights include a new SB-MANUAL contrib... og:url: https://daily.dev/posts/steel-bank-common-lisp-version-2-6-7-qsnxliuey og:image: https://api.daily.dev/og/posts/qSNXliuEy.png og:image:alt: Steel Bank Common Lisp version 2.6.7 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Steel Bank Common Lisp version 2.6.7 **[Hacker News](https://daily.dev/sources/hn)** · 432 min read · 0 upvotes · 0 comments ## Summary Release notes covering multiple recent versions of Steel Bank Common Lisp (SBCL), from version 2.5.3 through 2.6.7. Highlights include a new SB-MANUAL contrib module embedding the SBCL manual in docstrings for interactive exploration, AVX512 and ARM64 SIMD support, LoongArch architecture support, Windows ARM64 support, numerous compiler bug fixes (miscompilations, infinite loops, type derivation errors), and a wide range of performance optimizations including reduced consing, improved type inference, faster arithmetic operations, and better SIMD utilization for UTF-8 processing. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community take How the wider developer community reacted, aggregated from 1 discussion and 63 comments across hackernews (as of 2026-07-28). **TL;DR:** The community is broadly positive about SBCL's continued development, with excitement around new SIMD/ARM64 additions, while a lively side debate questions whether Lisp is practical for production use versus a niche or hobby language. **Sentiment:** 55% positive · 30% mixed · 15% skeptical **The case for** - SIMD support (ARM64 and AVX512) is seen as impressive new functionality. - Several commenters confirm real-world production use of Common Lisp, including at FAANG companies. - Clojure is cited as a Lisp with genuine traction that internalized lessons about macro discipline. - The image-based deployment model is compared favorably to modern Docker/AMI workflows. **The pushback** - Lisp's macro power and dynamic nature are argued to lead to fragmented ecosystems and unmaintainable DSLs. - Arena allocation feature lacks documentation in the official manual. - No auto-vectorization yet — SIMD intrinsics must be called explicitly. - CCL (Clozure CL) is seen as less actively maintained and lacks an ARM64 port. **By community** - hackernews (positive): Mostly enthusiastic about SBCL's technical progress, with a spirited but good-natured debate about Lisp's practical viability in production. **Hottest debate:** Whether Lisp's macro and dynamic features are a superpower or an ecosystem liability that dooms it to hobby/niche status. **Open questions** - When will SBCL support auto-vectorization? - Why is the memory arena feature still undocumented in the official manual? - What exactly is Cisco using Chez Scheme for? **Highlights** > Lisp's been around for 70 years at this point and hordes of developers tried it and said: lovely, but I ain't using it at work. I'm strongly convinced, having used Scheme, CL, Racket, Clojure that Lisp is doomed to be (mostly) a hobby language. The very power of Lisp, macros, dynamic programming, reflection lead to a mess of an ecosystem where every single developer reinvents the wheel and nobody can understand yet another DSL invented by the next developer next to them. Racket's theme of being a "programming language for building programming languages" is just the poster child of this naivety: I don't want even more friction. What scales and works is simple and boring. That's by the way why also Haskell has struggled forever. Beyond its dreadful DX, poor tooling and unacceptable compilation times, the language is just plagued by compiler extensions and every single developer reinventing its own abstractions. There was the simple haskell movement to just standardize around a set of extensions and conventions, but nope, these languages unavoidably attract people that want to stay in the ivory tower. Really, I love both lisps and haskell, but I would take a dreadful php over them every single day at work. No contest. > — [epolanski on hackernews · 6 comments](https://news.ycombinator.com/item?id=49088605) > I disagree with this profoundly. There is no argument that Lisp in general can get you in a terrible mess. So can C, or pretty much any language (I well remember a case of 11-way multiple inheritance in C++ game code). If I were running a Lisp-based project, there would be project standards (like no exported macros without signoff, and a list of standard library dependencies), documentation requirements, and code review. The fact that Lisp is the “programmable programming language” doesn't mean that every engineer should be inventing weird versions of while loops. What it does mean is that a skilled Lisp programmer can build a domain-specific language that substantially helps in development. One good example of this is the Crash Bandicoot games, along with the same studio's Jax and Daxter, which were built with dialects of Lisp (yes, they had to compile the code, and take care with storage allocation, just like any other game code). Cisco hired Kent Dybvig, principal author of the Chez Scheme system, and open-sourced that software; I have no clue what they use it for, to be honest, but I assume that they had some reason for doing this. Companies using various Lisp languages have been documented in areas from fintech to quantum computing. > — [vincent-manis on hackernews](https://news.ycombinator.com/item?id=49088913) > I was fortunate enough to use lisp professionally for nearly 20 years. The only reason that gig ended was the unfortunate demise of the majority owner and founder, and his heirs selling the shop to a competitor that only wanted the customer database imported. Lisp was never the problem, nor particularily messy. On the contrary, we considered it a major reason we were able to build a quite successful stock broker and bank from scratch with a team of 4-6 people, who doubled as datacenter ops (we ran on-prem), internal tech support for the rest of the firm (~20 people) and 2.line customer support. We quite naturally converged on a set of internal libraries for various tasks. Understanding and fixing each other’s code was not a big deal. Coincidentally, our frontend was php. That was messier, and we conciously kept that layer as lean as possible. > — [offlineguy on hackernews](https://news.ycombinator.com/item?id=49089857) > * 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? > — [wk\_end on hackernews · 2 comments](https://news.ycombinator.com/item?id=49087649) > Yeah I'm not sure why it's not in the manual, as it's had arena allocation support since at least 2.4.x, but basically: - use SB-VM:NEW-ARENA to make a new arena - use SB-VM:WITH-ARENA to redirect ordinary allocation into an existing arena like you would use WITH-OPEN-FILE or similar macros The only real doc is this internals note, and it doesn't even cover NEW-ARENA which I guess is left as an exercise to the reader: https://github.com/sbcl/sbcl/blob/master/doc/internals-notes... > — [stackghost on hackernews](https://news.ycombinator.com/item?id=49088657) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=49086971) · 79 points · 63 comments ## Similar posts on daily.dev - [Lisp: Common Lisp, Racket, Clojure, Emacs Lisp](https://daily.dev/posts/lisp-common-lisp-racket-clojure-emacs-lisp-jz1gvo1dc) · Lobsters · 0 upvotes · 0 comments - [SBCL Fibers: Lightweight Cooperative Threads](https://daily.dev/posts/sbcl-fibers-lightweight-cooperative-threads-zzn5jtjaa) · Hacker News · 0 upvotes · 0 comments - [Common Lisp Development Tooling](https://daily.dev/posts/common-lisp-development-tooling-jfw4xq8tk) · Hacker News · 0 upvotes · 0 comments - [SBCL: the ultimate assembly code breadboard](https://daily.dev/posts/sbcl-the-ultimate-assembly-code-breadboard-2fmr4vxfj) · Hacker News · 0 upvotes · 0 comments --- Tags: [#compiler-optimization](https://daily.dev/tags/compiler-optimization) [View this post on daily.dev](https://daily.dev/posts/steel-bank-common-lisp-version-2-6-7-qsnxliuey) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Steel Bank Common Lisp version 2.6.7","url":"https://daily.dev/posts/steel-bank-common-lisp-version-2-6-7-qsnxliuey","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/steel-bank-common-lisp-version-2-6-7-qsnxliuey"},"datePublished":"2026-07-28T18:38:44.500Z","dateModified":"2026-07-28T21:04:32.475Z","description":"Release notes covering multiple recent versions of Steel Bank Common Lisp (SBCL), from version 2.5.3 through 2.6.7. Highlights include a new SB-MANUAL contrib...","image":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","thumbnailUrl":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/steel-bank-common-lisp-version-2-6-7-qsnxliuey","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"compiler-optimization","timeRequired":"PT432M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Steel Bank Common Lisp version 2.6.7"}]} ```