logoalt Hacker News

Common Lisp Screenshots: today's CL applications in action

111 points • by _emacsomancer_ • last Thursday at 1:44 AM • 34 comments • view on HN

Comments

networked • today at 8:33 AM

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.
testermelon • today at 1:15 AM

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

Fr0styMatt88 • today at 1:35 AM

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.

➕ show 1 reply
tmtvl • yesterday at 11:42 AM

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.

➕ show 1 reply
bitwize • today at 4:00 AM

Lisp is aesthetics now. I used to appreciate the way in which its constructs gave the ordinary programmer considerably more reach. It made programming fun, the way I could talk directly to a running system and extend its functionality outwards with a minimum of boilerplate, procedures and data chasing each other's tails in a kind of neverending ouroboros.

But the fact is, whatever productivity gains I may have gained in Lisp are absolutely dwarfed by those gained by using an LLM. I have literally seen LLMs pointed at a problem, solve it almost instantly. And LLMs do better the more popular the programming language you're working in. So what's the point of choosing Lisp? Oh, your feeble human brain can understand the problem and craft a solution much more quickly and in a flow state without being bogged down by tedium? That's nice. Claude Code can understand the problem and craft a solution without you even being in the room. It's a cheat code. It's iddqd. It's "pay to win" for what used to be the challenging, demanding, and fun game of programming.

And Lisp went from being "still kinda the best programming language ever" to a retrocomputing curiosity almost overnight. There is no practical reason to start a new project in Lisp in 2026.

➕ show 7 replies