Dave Cooper (@dcooper) on GitLab, 2026-10-01.

Dave Cooper (@dcooper) on GitLab, 2026-10-01.

Dave Cooper Hi all, a proposed new common-lisp.net homepage is up for a look at https://common-lisp.net/facelift/ 2:19 PM Common-Lisp.net 2:20 PM Dave Cooper Any discussions on it can happen in #common-lisp.net channel, issues can go to clo/cl-site on our gitlab. 2:20 PM same content and URLs, a new look, a request form for GitLab accounts that actually reaches the admins, and a page on what the CLF is doing (fresh Docker images, arm64 CCL). 2:22 PM ⇐ attila_lendvai quit (~attila_le@2a02:ab88:850d:e400:baeb:d51a:9c42:998f) Ping timeout: 263 seconds 2:27 PM Daniel oh, ecl us pulled on docker quite often 2:28 PM the website looks nice 2:30 PM → digikar[m] joined (~digikarm]@user/digikarm:85827) 2:30 PM <digikar[m]> @digikar:matrix-for-lispers.net 1. Syntax highlighting 2:30 PM 2. May be JSCL in the browser? 2:32 PM Daniel there is jscl link 2:32 PM in start with liso 2:32 PM lusp* 2:32 PM eh 2:36 PM <digikar[m]> @digikar:matrix-for-lispers.net Found it. But it's 2 pages away. I feel 1 page away could be nice 2:38 PM → dra joined (~dra@user/dra) 2:38 PM <digikar[m]> @digikar:matrix-for-lispers.net 3. Would LEM be a better recommendation than Portacle? 2:42 PM → WinstonSchmitt joined (~WinstonSc@dynamic-176-005-082-056.176.5.pool.telefonica.de) 2:48 PM <digikar[m]> @digikar:matrix-for-lispers.net 4. ql-https has a one line install script, instead of the multiline install for quicklisp 2:48 PM 5. I couldn't easily find a link to portability.cl 2:48 PM 6. May be a link to metaspec or equivalent in the front page 2:49 PM 7. Each of the features section can link to another detailed documentation or video. Eg. You say it's fast, but how do I actually optimize my program? 2:49 PM 8. Link to ASDF documentation and best practices 2:52 PM ⇐ svr and gor-e quit
2:53 PM <digikar[m]> @digikar:matrix-for-lispers.net 9. I don't know how feasible it is. But a quicksearch:qs ability to search for libraries could be nice. 2:54 PM → gor-e joined (~gor-e@user/gor-e) 2:54 PM <digikar[m]> @digikar:matrix-for-lispers.net 10. And/Or a link to awesome-cl 3:00 PM → kchanqvq[m] joined (~kchanqvqm@static.253.225.104.178.clients.your-server.de) 3:00 PM <kchanqvq[m]> @kchanqvq:matrix-for-lispers.net I'm not sure if we should still recommending just installing quicklisp with its default dist. It has been 9 months without update. There are absolutely enough bug fixes in the last 9 month. 3:02 PM → mgl joined (~mgl@adsl-84-226-174-170.adslplus.ch) 3:03 PM <digikar[m]> @digikar:matrix-for-lispers.net But there's nothing else that provides any kind of guarantee that packages even load at a random hour, do they? Supplementing quicklisp with others would be nice though. 3:04 PM noOne there are 4-5 distros 3:04 PM → svr joined ⇐ WinstonSchmitt quit
3:05 PM noOne quicklisp/ultralisp/shirakumo/cl21 and some others 3:06 PM you can install most with quick-dist 3:06 PM <kchanqvq[m]> @kchanqvq:matrix-for-lispers.net imo ultralisp should provide a way to one-line install it (including quicklisp client) at the front page 3:06 PM ⇐ skin_ quit (~skin@165.225.10.85) Ping timeout: 243 seconds 3:07 PM noOne quicklisp is the container of all 3:07 PM ⇐ skin quit (~skin@165.225.10.103) Ping timeout: 240 seconds 3:07 PM <kchanqvq[m]> @kchanqvq:matrix-for-lispers.net I'm sure everyone here has a working CL environment but we need to think about new users 3:07 PM noOne any other dist gets pulled into quicklisps quicklisp/dists folder 3:07 PM ⇐ mgl quit (~mgl@adsl-84-226-174-170.adslplus.ch) Ping timeout: 247 seconds 3:07 PM noOne it's a prerequisite of any other so to say 3:08 PM <kchanqvq[m]> @kchanqvq:matrix-for-lispers.net That's what I have to tell every new user, goto SBCL website, do it, goto quicklisp website, do it, goto ultralisp website, do it 3:08 PM noOne some of the dists links don't work, that's why it can't get downloaded afaik 3:08 PM <kchanqvq[m]> @kchanqvq:matrix-for-lispers.net it's too many hops, cutting it into 2 hops would be already better 3:09 PM <digikar[m]> @digikar:matrix-for-lispers.net I think the point of contention is the default quicklisp dist. 3:11 PM Personally, I am not sure. A random new user probably does not need the latest library. And if they are collaborating with you, hopefully, you have a qlot / clpm / lock file 3:12 PM <kchanqvq[m]> @kchanqvq:matrix-for-lispers.net i'm considering them. I used to live happily with monthly quicklisp update 3:13 PM <digikar[m]> @digikar:matrix-for-lispers.net I'm okay with ultralisp if it provides the guarantee that the system loads 3:13 PM But I want to move towards pixi. That gets us easy installation of foreign libraries too. 3:16 PM noOne btw, quick-dist is on github, not part of quicklisp itself or any other afaik 3:17 PM so I installed that and got the other distros that way

Dave Cooper digikar[m]: How should we introduce LEM on the Getting Started page? (by the way the new site is live now at common-lisp.net) 9:05 AM minion: ask digikar: about LEM when he she or it shows up next time 9:06 AM no minion in here? 9:06 AM Daniel you advertise portacle, I'd assume that the request is to give lem the same placement 9:06 AM as a side note, I don't think that portacle is maintained 9:12 AM ⇐ bpanthi977 quit (~Thunderbi@2600:1010:a010:4ec:b502:89cc:1aaf:78a0) Ping timeout: 248 seconds 9:16 AM Dave Cooper jackdaniel: so how about we just drop Portacle from Getting Started (or demote it to a footnote), add LEM, and consider any other credible, currently maintained "quick-start" pathways. Can someone recommend a few sentences and a canonical link for LEM? 9:17 AM and more detailed discussion on common-lisp.net can happen in #common-lisp.net or in the Issues of gitlab.common-lisp.net/clo/cl-site

Dave Cooper (@dcooper) on GitLab, 2026-10-01.

Thanks to digikar, jackdaniel, kchanqvq and Inline. Where things stand:

1. Syntax highlighting — done. Code panels are coloured on the server, and each multi-line form folds to its first line (with Fold/Unfold above it).
2. JSCL closer — the front page now links it directly ("Try it in your browser").
3. Lem vs Portacle — Lem has its own card on Getting started. Portacle is now a footnote that says plainly it was last released in 2020.
4. ql-https one-liner — open; see the Quicklisp question below.
5. portability.cl — linked from Documentation and the libraries overview.
6. A spec beyond the CLHS — the CL Community Spec and Novaspec are now on the Documentation page, next to the HyperSpec.
7. Features linked to deeper material ("how do I actually optimize?") — agreed, and lodged as a larger piece of work. Suggestions for the best existing write-up or talk per feature are very welcome here.
8. ASDF docs and best practices — on Documentation, under "Systems and libraries", with the Cookbook's gentler page on systems.
9. Library search — lodged; for now the libraries overview points at Quickdocs.
10. awesome-cl — linked from Documentation, Community and the libraries overview.

Still open, and the reason this issue stays open: what Getting started should recommend for libraries. The Quicklisp dist hasn't updated in about nine months. Ultralisp, ocicl, qlot and quick-dist each answer part of that, and the question is whether the site recommends one, several or none. That needs the CLF board and the channel to weigh in. Please add your view here, or in

common-lisp.net.

Dave Cooper (@dcooper) on GitLab, 2026-10-01.

More commments:

<dcooper> Dave Cooper 
jackdaniel: so how about we just drop Portacle from Getting Started (or demote it to a footnote), add LEM, and consider any other credible, currently maintained "quick-start" pathways.  Can someone recommend a few sentences and a canonical link for LEM?
9:17 AM 
and more detailed discussion on common-lisp.net  can happen in #common-lisp.net or in the Issues of gitlab.common-lisp.net/clo/cl-site
9:26 AM 
→ bpanthi977 joined (~Thunderbi@2600:1010:a010:4ec:b502:89cc:1aaf:78a0)
9:27 AM <treflip> 
Shinmera: Cool! Is your workshop online or offline?
9:32 AM 
→ mgl_ joined  ↔ decweb popped in  
9:39 AM <_death> death 
if you add "LEM" newbies will ask for advice about it.. does anyone here actually use it?
9:45 AM 
→ mgl, X-Scale and edgar-rft joined  ⇐ mgl_ and edgar-rft` quit  
9:56 AM <jackdaniel> Daniel 
I don't personally think that lem is a good recommendation
9:57 AM 
just unpacking what digikar said
10:07 AM 
⇐ synchromesh quit (~john@2406:5a00:240a:2900:a691:b1ff:0:f9d) Read error: Connection reset by peer
10:09 AM <treflip> 
dcooper: I think it's worth mentioning "mine" lisp ide https://coalton-lang.github.io/20260424-mine/
10:09 AM <ixelp> 
Introducing mine, a Coalton and Common Lisp IDE
10:09 AM <treflip> 
It's made primarily for new lisp users as I understand
10:12 AM 
→ synchromesh joined  ↔ bpanthi977 nipped out  
10:15 AM <dcooper> Dave Cooper 
https://gitlab.common-lisp.net/clo/cl-site/-/work_items/44
10:15 AM <ixelp> 
Making sure you're not a bot!
10:16 AM <dcooper> Dave Cooper 
suggestions from here are being tracked in this 👆🏻  issue.

Dave Cooper (@dcooper) on GitLab, 2026-10-01.

If I may, I'd like to suggest that the Common Lisp Metaspec (https://metaspec.dev/) has superseded the CLHS in every way and should replace it as the free alternative. 9:53 AM → edgar-rft joined ⇐ edgar-rft` quit
dcooper New message input

Dave Cooper (@dcooper) on GitLab, 2026-10-01.

Correction to item 6 above: digikar meant the Common Lisp Metaspec, not a spec in general. It now heads the specification section of the Documentation page as the reference to read; the Community Spec, Novaspec and the PDF follow as other renderings of the same draft, and the HyperSpec stays as the edition older material links to. Thanks to dlowe for the nudge in #common-lisp.net.