Why I Chose Common Lisp
(djhaskin.com)
After ~7 years, I was done with Clojure. I was writing a some CLI apps, and I hated how long they took to start up. The community at large seemed not to care about this problem, except for the babashka folks. However, I spent long, hard hours banging my head against native-image and it just wasn't working out. It was incredibly painful, and at the end of it, I still didn't have standalone, fast-starting native executables.
After ~7 years, I was done with Clojure. I was writing a some CLI apps, and I hated how long they took to start up. The community at large seemed not to care about this problem, except for the babashka folks. However, I spent long, hard hours banging my head against native-image and it just wasn't working out. It was incredibly painful, and at the end of it, I still didn't have standalone, fast-starting native executables.
A Closed and Common Lisp (2021)
(flooey.org)
I just recently finished up Advent of Code for 2021, and, like last year, I did it in a new-to-me language. This year’s choice was Common Lisp. My total previous exposure to Lisp was a couple weeks writing Scheme in my Programming Languages class at university, so it was almost entirely a novel experience.
I just recently finished up Advent of Code for 2021, and, like last year, I did it in a new-to-me language. This year’s choice was Common Lisp. My total previous exposure to Lisp was a couple weeks writing Scheme in my Programming Languages class at university, so it was almost entirely a novel experience.
OCRing Music from YouTube with Common Lisp
(nickfa.ro)
There's a tune on YouTube I always really liked called "Supersquatting." It was written by Dubmood and Zabutom, two really masterful chiptune composers, but this track always stood out to me as sounding really full and "fat."
There's a tune on YouTube I always really liked called "Supersquatting." It was written by Dubmood and Zabutom, two really masterful chiptune composers, but this track always stood out to me as sounding really full and "fat."
The Long, Painful History of Time (1999)
(naggum.no)
The programming language Common Lisp offers a few functions to support the concept of time as humans experience it, including GET-UNIVERSAL-TIME, ENCODE-UNIVERSAL-TIME, DECODE-UNIVERSAL-TIME, and GET-DECODED-TIME. These functions assume the existence of a timezone and a daylight saving time regime, such that they can support the usual expression of time in the environment in which a small number of real-life applications run.
The programming language Common Lisp offers a few functions to support the concept of time as humans experience it, including GET-UNIVERSAL-TIME, ENCODE-UNIVERSAL-TIME, DECODE-UNIVERSAL-TIME, and GET-DECODED-TIME. These functions assume the existence of a timezone and a daylight saving time regime, such that they can support the usual expression of time in the environment in which a small number of real-life applications run.
Common Lisp implementation of the Forth 2012 Standard
(github.com/gmpalter)
Common Lisp implementation of the Forth 2012 Standard, CL-Forth
Common Lisp implementation of the Forth 2012 Standard, CL-Forth
AP5 - Declarative Programming Library For Common Lisp (1995)
(oceanpark.com)
This is a ruthlessly abridged presentation of AP5, a high level language, currently implemented as an extension to Common Lisp. I write this to communicate my discovery of a good language to others. Everything described is implemented.
This is a ruthlessly abridged presentation of AP5, a high level language, currently implemented as an extension to Common Lisp. I write this to communicate my discovery of a good language to others. Everything described is implemented.