{"slug": "sbcl", "name": "SBCL", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "Steel Bank Common Lisp, an open-source, high-performance native-code compiler and implementation of Common Lisp.", "recommenders": 6, "commenters": 7, "warners": 0, "score": 5.97, "rising": 3.35, "first": "2026-07-10", "latest": "2026-08-12", "why": "Recommended as arguably the best Common Lisp implementation for its mature compiler and garbage collection, and used for hobby projects, web backends and fast-starting command-line tools.", "why_is_quote": false, "has_verdict": true, "sentiment": {"recommend": 5, "neutral": 2, "compare": 0, "warn": 0}, "spark": [0, 0, 0, 0, 0, 0, 0, 0, 1, 4, 0, 0], "listed": true, "loved": ["Mature compiler", "Web backends"], "caveat": "Shell command overhead", "short_quote": "Arguably the best is SBCL, which has a mature compiler and garbage collection.", "icon": false, "domain": null, "github_repo": null, "official_url": "https://www.sbcl.org/", "pricing": "open source", "aliases": ["SBCL"], "verdict": [{"text": "Recommended as arguably the best Common Lisp implementation for its mature compiler and garbage collection,", "cites": [{"id": 787896576, "item_id": 49243536, "url": "https://news.ycombinator.com/item?id=49243536", "by": "stackghost", "date": "2026-08-10", "stance": "recommend", "quote": "Arguably the best is SBCL, which has a mature compiler and garbage collection.", "excerpt": "\"Lisp\" refers to several different languages in the same family, which contributes to the confusion. Perhaps the default choice is Common Lisp which itself is specified in an ANSI standard and has several competing implementations. Some are compiled, some are interpreted. Arguably the best is SBCL, which has a mature compiler and garbage collection. If you lean on implementation-specific features you can produce extr", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Because It's Not Fun Enough: why languages fail"}, {"id": 787915536, "item_id": 49244721, "url": "https://news.ycombinator.com/item?id=49244721", "by": "stackghost", "date": "2026-08-10", "stance": "recommend", "quote": "Arguably the best is SBCL", "excerpt": ">The best is kind of debatable I used the word \"arguably\" in the very first word of that sentence: >Arguably the best is SBCL The word arguable is a synonym for the word debatable.", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Because It's Not Fun Enough: why languages fail"}, {"id": 788486064, "item_id": 49280379, "url": "https://news.ycombinator.com/item?id=49280379", "by": "kodoman", "date": "2026-08-12", "stance": "recommend", "quote": "SBCL is a fantastic project and compiler", "excerpt": "I have been using cl for a project recently, as it had many features I wanted and actually made sense to use despite not being familiar with it (though used elisp and a tiny bit of scheme). I found it mixed some things where fantastic some things remain pain points, SBCL is a fantastic project and compiler and once you get used to the debugging it's a very nice experience with slime. It is true to say that it's flexi", "context": "", "use_case": "Common Lisp project", "switched_from": "", "story": "Why vibe code in Common Lisp?"}]}, {"text": " and used for hobby projects, web backends and fast-starting command-line tools.", "cites": [{"id": 788507712, "item_id": 49281732, "url": "https://news.ycombinator.com/item?id=49281732", "by": "GeorgeTirebiter", "date": "2026-08-12", "stance": "recommend", "quote": "I now generate ALL of my hobby projects in CL (SBCL on windows).", "excerpt": "I suggest Practical Common Lisp by Seibel https://gigamonkeys.com/book/ I now generate ALL of my hobby projects in CL (SBCL on windows). I tell the LLM to 'over-comment' the code, so I get to learn as I read the output. It has been glorious. I generally use the web browser on an unused port on localhost for user IO (beautiful pages), and the app just hooks to Hunchentoot to serve. Any 'real' programming language (mea", "context": "hobby programmer", "use_case": "hobby projects with LLM-generated code", "switched_from": "", "story": "Why vibe code in Common Lisp?"}, {"id": 785672272, "item_id": 49104517, "url": "https://news.ycombinator.com/item?id=49104517", "by": "Jach", "date": "2026-07-29", "stance": "recommend", "quote": "Hacker News itself runs fine on SBCL", "excerpt": "You can use most of the popular GUI libs, there's a couple Lisp-specific ones but they're not nearly as featureful. https://lispcookbook.github.io/cl-cookbook/gui.html collects most of them; though for gtk4 I'd recommend https://github.com/crategus/cl-cffi-gtk4/ But no matter what you use I think the experience is going to be a bit rough. CLOG is probably the most interesting non-traditional framework but you do have", "context": "", "use_case": "backend services", "switched_from": "", "story": "Steel Bank Common Lisp version 2.6.7"}, {"id": 785455392, "item_id": 49090962, "url": "https://news.ycombinator.com/item?id=49090962", "by": "mark_l_watson", "date": "2026-07-28", "stance": "recommend", "quote": "I used to do this to build command line utilities in SBCL, with millisecond initialization times.", "excerpt": "I used to do this to build command line utilities in SBCL, with millisecond initialization times. Good technique, and compress the image so executables are fairly small.", "context": "", "use_case": "command line utilities", "switched_from": "", "story": "Steel Bank Common Lisp version 2.6.7"}]}, {"text": " The main caveat is slow, serialized shell commands when running with a large heap,", "cites": [{"id": 788486432, "item_id": 49280402, "url": "https://news.ycombinator.com/item?id=49280402", "by": "sillysaurusx", "date": "2026-08-12", "stance": "neutral", "quote": "One annoying part of SBCL is that it does something up front with its memory", "excerpt": "One annoying part of SBCL is that it does something up front with its memory such that if you run it with an 8GB heap, running shell commands takes a noticeably long time even for \"echo hi\". It\u2019s something to do with the way it forks. Shell commands are also serialized, meaning multiple threads running curl won\u2019t help you more than a single thread running curl. This is in contrast to almost every other programming la", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Why vibe code in Common Lisp?"}]}, {"text": " and idiomatic, portable code is slower than implementation-specific tuned code.", "cites": [{"id": 787896576, "item_id": 49243536, "url": "https://news.ycombinator.com/item?id=49243536", "by": "stackghost", "date": "2026-08-10", "stance": "recommend", "quote": "Arguably the best is SBCL, which has a mature compiler and garbage collection.", "excerpt": "\"Lisp\" refers to several different languages in the same family, which contributes to the confusion. Perhaps the default choice is Common Lisp which itself is specified in an ANSI standard and has several competing implementations. Some are compiled, some are interpreted. Arguably the best is SBCL, which has a mature compiler and garbage collection. If you lean on implementation-specific features you can produce extr", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Because It's Not Fun Enough: why languages fail"}]}], "praise": [{"label": "Mature compiler", "summary": "Commenters call it arguably the best Common Lisp implementation, with a mature compiler and garbage collection.", "quotes": [{"id": 787896576, "item_id": 49243536, "url": "https://news.ycombinator.com/item?id=49243536", "by": "stackghost", "date": "2026-08-10", "stance": "recommend", "quote": "Arguably the best is SBCL, which has a mature compiler and garbage collection.", "excerpt": "\"Lisp\" refers to several different languages in the same family, which contributes to the confusion. Perhaps the default choice is Common Lisp which itself is specified in an ANSI standard and has several competing implementations. Some are compiled, some are interpreted. Arguably the best is SBCL, which has a mature compiler and garbage collection. If you lean on implementation-specific features you can produce extr", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Because It's Not Fun Enough: why languages fail"}, {"id": 787915536, "item_id": 49244721, "url": "https://news.ycombinator.com/item?id=49244721", "by": "stackghost", "date": "2026-08-10", "stance": "recommend", "quote": "Arguably the best is SBCL", "excerpt": ">The best is kind of debatable I used the word \"arguably\" in the very first word of that sentence: >Arguably the best is SBCL The word arguable is a synonym for the word debatable.", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Because It's Not Fun Enough: why languages fail"}, {"id": 788486064, "item_id": 49280379, "url": "https://news.ycombinator.com/item?id=49280379", "by": "kodoman", "date": "2026-08-12", "stance": "recommend", "quote": "SBCL is a fantastic project and compiler", "excerpt": "I have been using cl for a project recently, as it had many features I wanted and actually made sense to use despite not being familiar with it (though used elisp and a tiny bit of scheme). I found it mixed some things where fantastic some things remain pain points, SBCL is a fantastic project and compiler and once you get used to the debugging it's a very nice experience with slime. It is true to say that it's flexi", "context": "", "use_case": "Common Lisp project", "switched_from": "", "story": "Why vibe code in Common Lisp?"}]}, {"label": "Web backends", "summary": "Commenters say it is a good fit for backends, noting Hacker News itself runs on it and apps can serve pages via Hunchentoot.", "quotes": [{"id": 785672272, "item_id": 49104517, "url": "https://news.ycombinator.com/item?id=49104517", "by": "Jach", "date": "2026-07-29", "stance": "recommend", "quote": "Hacker News itself runs fine on SBCL", "excerpt": "You can use most of the popular GUI libs, there's a couple Lisp-specific ones but they're not nearly as featureful. https://lispcookbook.github.io/cl-cookbook/gui.html collects most of them; though for gtk4 I'd recommend https://github.com/crategus/cl-cffi-gtk4/ But no matter what you use I think the experience is going to be a bit rough. CLOG is probably the most interesting non-traditional framework but you do have", "context": "", "use_case": "backend services", "switched_from": "", "story": "Steel Bank Common Lisp version 2.6.7"}, {"id": 788507712, "item_id": 49281732, "url": "https://news.ycombinator.com/item?id=49281732", "by": "GeorgeTirebiter", "date": "2026-08-12", "stance": "recommend", "quote": "I now generate ALL of my hobby projects in CL (SBCL on windows).", "excerpt": "I suggest Practical Common Lisp by Seibel https://gigamonkeys.com/book/ I now generate ALL of my hobby projects in CL (SBCL on windows). I tell the LLM to 'over-comment' the code, so I get to learn as I read the output. It has been glorious. I generally use the web browser on an unused port on localhost for user IO (beautiful pages), and the app just hooks to Hunchentoot to serve. Any 'real' programming language (mea", "context": "hobby programmer", "use_case": "hobby projects with LLM-generated code", "switched_from": "", "story": "Why vibe code in Common Lisp?"}]}, {"label": "Performance", "summary": "Code that relies on implementation-specific features can approach C performance in some benchmarks.", "quotes": [{"id": 787896576, "item_id": 49243536, "url": "https://news.ycombinator.com/item?id=49243536", "by": "stackghost", "date": "2026-08-10", "stance": "recommend", "quote": "Arguably the best is SBCL, which has a mature compiler and garbage collection.", "excerpt": "\"Lisp\" refers to several different languages in the same family, which contributes to the confusion. Perhaps the default choice is Common Lisp which itself is specified in an ANSI standard and has several competing implementations. Some are compiled, some are interpreted. Arguably the best is SBCL, which has a mature compiler and garbage collection. If you lean on implementation-specific features you can produce extr", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Because It's Not Fun Enough: why languages fail"}]}, {"label": "Fast CLI startup", "summary": "Saved images give command-line utilities millisecond startup times and fairly small compressed executables.", "quotes": [{"id": 785455392, "item_id": 49090962, "url": "https://news.ycombinator.com/item?id=49090962", "by": "mark_l_watson", "date": "2026-07-28", "stance": "recommend", "quote": "I used to do this to build command line utilities in SBCL, with millisecond initialization times.", "excerpt": "I used to do this to build command line utilities in SBCL, with millisecond initialization times. Good technique, and compress the image so executables are fairly small.", "context": "", "use_case": "command line utilities", "switched_from": "", "story": "Steel Bank Common Lisp version 2.6.7"}]}, {"label": "Interactive debugging", "summary": "Once you get used to it, debugging with SLIME is described as a very nice experience.", "quotes": [{"id": 788486064, "item_id": 49280379, "url": "https://news.ycombinator.com/item?id=49280379", "by": "kodoman", "date": "2026-08-12", "stance": "recommend", "quote": "SBCL is a fantastic project and compiler", "excerpt": "I have been using cl for a project recently, as it had many features I wanted and actually made sense to use despite not being familiar with it (though used elisp and a tiny bit of scheme). I found it mixed some things where fantastic some things remain pain points, SBCL is a fantastic project and compiler and once you get used to the debugging it's a very nice experience with slime. It is true to say that it's flexi", "context": "", "use_case": "Common Lisp project", "switched_from": "", "story": "Why vibe code in Common Lisp?"}]}, {"label": "Works on Windows", "summary": "One hobbyist uses it on Windows for all of their projects.", "quotes": [{"id": 788507712, "item_id": 49281732, "url": "https://news.ycombinator.com/item?id=49281732", "by": "GeorgeTirebiter", "date": "2026-08-12", "stance": "recommend", "quote": "I now generate ALL of my hobby projects in CL (SBCL on windows).", "excerpt": "I suggest Practical Common Lisp by Seibel https://gigamonkeys.com/book/ I now generate ALL of my hobby projects in CL (SBCL on windows). I tell the LLM to 'over-comment' the code, so I get to learn as I read the output. It has been glorious. I generally use the web browser on an unused port on localhost for user IO (beautiful pages), and the app just hooks to Hunchentoot to serve. Any 'real' programming language (mea", "context": "hobby programmer", "use_case": "hobby projects with LLM-generated code", "switched_from": "", "story": "Why vibe code in Common Lisp?"}]}], "caveats": [{"label": "Shell command overhead", "summary": "With a large heap, such as 8GB, running even simple shell commands is noticeably slow because of how it forks.", "quotes": [{"id": 788486432, "item_id": 49280402, "url": "https://news.ycombinator.com/item?id=49280402", "by": "sillysaurusx", "date": "2026-08-12", "stance": "neutral", "quote": "One annoying part of SBCL is that it does something up front with its memory", "excerpt": "One annoying part of SBCL is that it does something up front with its memory such that if you run it with an 8GB heap, running shell commands takes a noticeably long time even for \"echo hi\". It\u2019s something to do with the way it forks. Shell commands are also serialized, meaning multiple threads running curl won\u2019t help you more than a single thread running curl. This is in contrast to almost every other programming la", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Why vibe code in Common Lisp?"}]}, {"label": "Serialized subprocesses", "summary": "Shell commands are serialized, so running curl from multiple threads gives no speedup.", "quotes": [{"id": 788486432, "item_id": 49280402, "url": "https://news.ycombinator.com/item?id=49280402", "by": "sillysaurusx", "date": "2026-08-12", "stance": "neutral", "quote": "One annoying part of SBCL is that it does something up front with its memory", "excerpt": "One annoying part of SBCL is that it does something up front with its memory such that if you run it with an 8GB heap, running shell commands takes a noticeably long time even for \"echo hi\". It\u2019s something to do with the way it forks. Shell commands are also serialized, meaning multiple threads running curl won\u2019t help you more than a single thread running curl. This is in contrast to almost every other programming la", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Why vibe code in Common Lisp?"}]}, {"label": "Portable code slower", "summary": "Idiomatic, portable Lisp is slower in practice than code tuned with implementation-specific features.", "quotes": [{"id": 787896576, "item_id": 49243536, "url": "https://news.ycombinator.com/item?id=49243536", "by": "stackghost", "date": "2026-08-10", "stance": "recommend", "quote": "Arguably the best is SBCL, which has a mature compiler and garbage collection.", "excerpt": "\"Lisp\" refers to several different languages in the same family, which contributes to the confusion. Perhaps the default choice is Common Lisp which itself is specified in an ANSI standard and has several competing implementations. Some are compiled, some are interpreted. Arguably the best is SBCL, which has a mature compiler and garbage collection. If you lean on implementation-specific features you can produce extr", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Because It's Not Fun Enough: why languages fail"}]}, {"label": "Learning curve", "summary": "Its debugging workflow takes some getting used to.", "quotes": [{"id": 788486064, "item_id": 49280379, "url": "https://news.ycombinator.com/item?id=49280379", "by": "kodoman", "date": "2026-08-12", "stance": "recommend", "quote": "SBCL is a fantastic project and compiler", "excerpt": "I have been using cl for a project recently, as it had many features I wanted and actually made sense to use despite not being familiar with it (though used elisp and a tiny bit of scheme). I found it mixed some things where fantastic some things remain pain points, SBCL is a fantastic project and compiler and once you get used to the debugging it's a very nice experience with slime. It is true to say that it's flexi", "context": "", "use_case": "Common Lisp project", "switched_from": "", "story": "Why vibe code in Common Lisp?"}]}], "who": [{"by": "GeorgeTirebiter", "context": "hobby programmer", "url": "https://news.ycombinator.com/item?id=49281732", "date": "2026-08-12"}, {"by": "drob518", "context": "Clojure daily driver", "url": "https://news.ycombinator.com/item?id=49259240", "date": "2026-08-11"}], "tags": ["for hobby projects", "for web backends", "for command-line tools", "for Windows users", "for LLM-assisted coding"], "use_cases": ["common lisp implementation", "hobby projects with llm-generated code", "common lisp project", "backend services", "command line utilities", "running common lisp tests"], "compared": [], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49269429", "title": "Why vibe code in Common Lisp?", "mentions": 3}, {"url": "https://news.ycombinator.com/item?id=49242245", "title": "Because It's Not Fun Enough: why languages fail", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49086971", "title": "Steel Bank Common Lisp version 2.6.7", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49251702", "title": "Chicken Scheme 6.0 Released", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48845209", "title": "A Road to Lisp: Why Lisp", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {"neutral": 1, "recommend": 1}, "2026-08": {"recommend": 4, "neutral": 1}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 788507712, "item_id": 49281732, "url": "https://news.ycombinator.com/item?id=49281732", "by": "GeorgeTirebiter", "date": "2026-08-12", "stance": "recommend", "quote": "I now generate ALL of my hobby projects in CL (SBCL on windows).", "excerpt": "I suggest Practical Common Lisp by Seibel https://gigamonkeys.com/book/ I now generate ALL of my hobby projects in CL (SBCL on windows). I tell the LLM to 'over-comment' the code, so I get to learn as I read the output. It has been glorious. I generally use the web browser on an unused port on localhost for user IO (beautiful pages), and the app just hooks to Hunchentoot to serve. Any 'real' programming language (mea", "context": "hobby programmer", "use_case": "hobby projects with LLM-generated code", "switched_from": "", "story": "Why vibe code in Common Lisp?"}, {"id": 788486432, "item_id": 49280402, "url": "https://news.ycombinator.com/item?id=49280402", "by": "sillysaurusx", "date": "2026-08-12", "stance": "neutral", "quote": "One annoying part of SBCL is that it does something up front with its memory", "excerpt": "One annoying part of SBCL is that it does something up front with its memory such that if you run it with an 8GB heap, running shell commands takes a noticeably long time even for \"echo hi\". It\u2019s something to do with the way it forks. Shell commands are also serialized, meaning multiple threads running curl won\u2019t help you more than a single thread running curl. This is in contrast to almost every other programming la", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Why vibe code in Common Lisp?"}, {"id": 788486064, "item_id": 49280379, "url": "https://news.ycombinator.com/item?id=49280379", "by": "kodoman", "date": "2026-08-12", "stance": "recommend", "quote": "SBCL is a fantastic project and compiler", "excerpt": "I have been using cl for a project recently, as it had many features I wanted and actually made sense to use despite not being familiar with it (though used elisp and a tiny bit of scheme). I found it mixed some things where fantastic some things remain pain points, SBCL is a fantastic project and compiler and once you get used to the debugging it's a very nice experience with slime. It is true to say that it's flexi", "context": "", "use_case": "Common Lisp project", "switched_from": "", "story": "Why vibe code in Common Lisp?"}, {"id": 788147840, "item_id": 49259240, "url": "https://news.ycombinator.com/item?id=49259240", "by": "drob518", "date": "2026-08-11", "stance": "recommend", "quote": "go to CL and then use something like SBCL", "excerpt": "That dynamic was exactly why I moved from Scheme to CL many years ago (full disclosure, Clojure is my daily driver, now). I loved the minimalism of the RxRS documents, but they really only covered the small core of the language, and then all the implementations were completely different when it came to libraries. And those differences always needed to be understood in order to write real-world programs. SRFIs helped,", "context": "Clojure daily driver", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Chicken Scheme 6.0 Released"}, {"id": 787915536, "item_id": 49244721, "url": "https://news.ycombinator.com/item?id=49244721", "by": "stackghost", "date": "2026-08-10", "stance": "recommend", "quote": "Arguably the best is SBCL", "excerpt": ">The best is kind of debatable I used the word \"arguably\" in the very first word of that sentence: >Arguably the best is SBCL The word arguable is a synonym for the word debatable.", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Because It's Not Fun Enough: why languages fail"}, {"id": 787896576, "item_id": 49243536, "url": "https://news.ycombinator.com/item?id=49243536", "by": "stackghost", "date": "2026-08-10", "stance": "recommend", "quote": "Arguably the best is SBCL, which has a mature compiler and garbage collection.", "excerpt": "\"Lisp\" refers to several different languages in the same family, which contributes to the confusion. Perhaps the default choice is Common Lisp which itself is specified in an ANSI standard and has several competing implementations. Some are compiled, some are interpreted. Arguably the best is SBCL, which has a mature compiler and garbage collection. If you lean on implementation-specific features you can produce extr", "context": "", "use_case": "Common Lisp implementation", "switched_from": "", "story": "Because It's Not Fun Enough: why languages fail"}, {"id": 785672272, "item_id": 49104517, "url": "https://news.ycombinator.com/item?id=49104517", "by": "Jach", "date": "2026-07-29", "stance": "recommend", "quote": "Hacker News itself runs fine on SBCL", "excerpt": "You can use most of the popular GUI libs, there's a couple Lisp-specific ones but they're not nearly as featureful. https://lispcookbook.github.io/cl-cookbook/gui.html collects most of them; though for gtk4 I'd recommend https://github.com/crategus/cl-cffi-gtk4/ But no matter what you use I think the experience is going to be a bit rough. CLOG is probably the most interesting non-traditional framework but you do have", "context": "", "use_case": "backend services", "switched_from": "", "story": "Steel Bank Common Lisp version 2.6.7"}, {"id": 785455392, "item_id": 49090962, "url": "https://news.ycombinator.com/item?id=49090962", "by": "mark_l_watson", "date": "2026-07-28", "stance": "recommend", "quote": "I used to do this to build command line utilities in SBCL, with millisecond initialization times.", "excerpt": "I used to do this to build command line utilities in SBCL, with millisecond initialization times. Good technique, and compress the image so executables are fairly small.", "context": "", "use_case": "command line utilities", "switched_from": "", "story": "Steel Bank Common Lisp version 2.6.7"}, {"id": 781807616, "item_id": 48862976, "url": "https://news.ycombinator.com/item?id=48862976", "by": "mark_l_watson", "date": "2026-07-10", "stance": "neutral", "quote": "I specify in, for examp,e, my Common Lisp skills file to run \u2018sbcl -load \u2026\u201d", "excerpt": "I use LLM_based coding agents frequently with Lisp languages and my way of working is different with Lisp languages: 1) if generated code ever has a syntax error, I like to quickly fix the syntax error myself. 2) for some reason I usually prefer to run tests myself in another terminal (with Python, Typescript, etc. I let the coding harness run tests). I haven\u2019t let coding harnesses run REPLs. When I do let a coding h", "context": "", "use_case": "running Common Lisp tests", "switched_from": "", "story": "A Road to Lisp: Why Lisp"}]}