Common Lisp Screenshots: today's CL applications in action
lisp-screenshots.orgGitHub 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.(including HN! - https://media.simple.photo/12M3xnh3VhDMUgCs8DVhkTBI6OgDGGIX/... )
Indeed, Arc's been running on Common Lisp for a while now!
Too bad the screenshot doesn't show this page as a nice autoreference mise en abîme.
I like how the disclaimer went humble bragging about the range of usage.
>"Please don't assume Lisp is only useful for Animation and Graphics, AI, Bioinformatics, B2B and Ecommerce, Data Mining, EDA/Semiconductor applications, Expert Systems, Finance, Intelligent Agents, Knowledge Management, Mechanical CAD, Modeling and Simulation, Natural Language, Optimization, Research, Risk Analysis, Scheduling, Telecom, and Web Authoring just because these are the only things they happened to list."
>Kent Pitman
He left out Guessing Animals!
https://en.wikipedia.org/wiki/Kent_Pitman
>While in high school, he saw output from one of the guess the animal pseudo-artificial intelligence (AI) games then popular. He considered implementing a version of the program in BASIC, but once at the Massachusetts Institute of Technology (MIT), instead he implemented it in several dialects of Lisp, including Maclisp.
Kent Pitman's Lisp Eliza from MIT-AI's ITS History Project (sites.google.com)
https://news.ycombinator.com/item?id=39373567
https://sites.google.com/view/elizagen-org
https://climatejustice.social/@kentpitman/111236824217096297
https://web.archive.org/web/20131102031307/http://open.salon...
The core route optimization algorithm of Routific is also written in Common Lisp :)
That's awesome, thank you. How do you know it, is there a reference on the net somewhere?
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.
Thank you, TLS should be fine now. (fixed ±12 hours ago)
Many of them do say which program they are from; at least the first of multiple are from the same program.
Yeah, turns out that feature is gated behind javascript, which is unfortunate. The website works pretty well otherwise.
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.
Nowadays it also supports .NET, COM and ObjectARX.
Just like Gimp eventually added support to Python alongside Script-Fu.
Which end up reducing the interest to reach out to Lisp languages.
Were it not for early exposure to Autolisp I would not have appreciated Lisp or Lisp-based systems, like Emacs, the way that I did. I might've ended up whinging that they didn't use a mOdErN language like JavaScript.
Autolisp definitely sent me down the left-paren path.