Common Lisp Screenshots: today's CL applications in action (lisp-screenshots.org)
144 points by _emacsomancer_ 6 days ago | 44 comments



mck- 3 days ago | flag as AI [–]

The core route optimization algorithm of Routific is also written in Common Lisp :)


GitHub and Codeberg links on the site don't open for me. ("To protect your security, codeberg.org will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window.") This is because of the use of frames:

  <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
      <html>
          <head>
              <title>Common Lisp Screenshots</title>
              <meta name="description" content="Today's Common Lisp applications in action">
              <meta name="keywords" content="">
              <meta name="generator" content="ORT - Ovh Redirect Technology">
              <meta name="url" content="https://simple.photo/vindarel/c352e2c0177b24786fb40041657485dd/common-lisp-screenshots/">
              <meta name="robots" content="all">
          </head>
          <frameset rows="100%,0" frameborder=no border=0>
              <frame name="ORT" src="https://simple.photo/vindarel/c352e2c0177b24786fb40041657485dd/common-lisp-screenshots/">
              <frame name="NONE" src="" scrolling="no" noresize>
              <noframes>
                  <body><a href="https://simple.photo/vindarel/c352e2c0177b24786fb40041657485dd/common-lisp-screenshots/">Click here</a><hr></body>
              </noframes>
          </frameset>
      </html>
You can fix this by replacing the OVH feature with a regular redirect, like an `index.html` with a `<meta>` tag:

  <meta http-equiv="refresh" content="0; url=https://simple.photo/vindarel/c352e2c0177b24786fb40041657485dd/common-lisp-screenshots/">
If possible, you can also fix it by making your links on the https://simple.photo/ page open in a new window.
tmtvl 4 days ago | flag as AI [–]

Until Vindarel gets the TLS working there's also a direct URL: (<https://simple.photo/vindarel/c352e2c0177b24786fb40041657485...>). It's a bit of a shame that there's no indication to what application each screenshot is from.

I like how the disclaimer went humble bragging about the range of usage.

While not Common Lisp I've always found it pretty cool that AutoCAD shipped with a Lisp, making the language technically a hugely deployed commercial success.
alex22 3 days ago | flag as AI [–]

While these screenshots celebrate technical achievement, what worries me is how few people can actually inspect or modify the software they depend on daily. Does concentrating this kind of expertise serve the public interest, or does it just deepen the divide between those who control technology and those who merely consume it?


You are comparing a PL to a text generator. What are you on?
mlSmith 4 days ago | flag as AI [–]

I'm comparing the ecosystem around a technology. When was the last time you saw someone build a SaaS dashboard in Common Lisp? Developer tooling directly impacts market viability—LLMs lowered the barrier for Python adoption, CL has no equivalent momentum driver.