{"id":595971,"date":"2023-01-10T05:49:57","date_gmt":"2023-01-10T11:49:57","guid":{"rendered":"https:\/\/news.sellorbuyhomefast.com\/index.php\/2023\/01\/10\/common-lisp-2022-in-review\/"},"modified":"2023-01-10T05:49:57","modified_gmt":"2023-01-10T11:49:57","slug":"common-lisp-2022-in-review","status":"publish","type":"post","link":"https:\/\/newsycanuse.com\/index.php\/2023\/01\/10\/common-lisp-2022-in-review\/","title":{"rendered":"Common Lisp: 2022 in review"},"content":{"rendered":"
\n

And 2022 is over. The Common Lisp language and environment are solid
\nand stable, yet evolve. Implementations, go-to libraries, best
\npractices, communities evolve. We don\u2019t need a \u201cState of the
\nEcosystem\u201d every two weeks but still, what happened and what did you
\nmiss in 2022?<\/p>\n

This is my pick of the most exciting, fascinating, interesting or just
\ncool projects, tools, libraries and articles that popped-up during
\nthat time (with a few exceptions that appeared in late 2021).<\/p>\n

This overview is not a \u201cState of the CL ecosystem\u201d<\/a> (HN comments (133)<\/a>) that I did in
\n2020, for which you can find complementary comments on HN.<\/p>\n

\n

I think this article (of sorts) is definitely helpful for onlookers to Common Lisp, but doesn\u2019t provide the full \u201cstory\u201d or \u201cfeel\u201d of Common Lisp, and I want to offer to HN my own perspective.<\/p>\n<\/blockquote>\n

And, suffice to say, I tried to talk about the most important things,
\nbut this article (of sorts) is by no means a compilation of all<\/em> new
\nCL projects or all the articles published on the internet. Look on
\nReddit, Quicklisp releases, Github, and my favourite resources:<\/p>\n