"Common Lisp is not a beautiful crystal of programming language design. It's a scruffy workshop with a big pegboard wall of tools, a thin layer of sawdust on the floor, a filing cabinet in the office with a couple of drawers that open perpendicular to the rest, [...]"
"This historical baggage is a price paid to ensure Common Lisp had a future."
In this video, I'll give you 5 reasons why I think you should learn Scheme this year! Regardless if you are a programming beginner or an expert hacker, there is a lot to be gained from learning this language.
In this post Michał Herda explained what Lisp programmers intuitively know.
The parentheses don't bother Lisp programmers as they read code by its indentation and rely on Lisp-aware tools such as editors and IDEs, which match parentheses and properly indent code.
If you've got questions about Emacs, Guix, Guile, or other related topics and want a friendly place to ask them, come check out the new System Crafters Forum!
I love how Dan Weinreb's reasons for why #Symbolics didn't succeed doesn't even consider their hostility towards free and open development of #LispMachine software as having something to do with it.
I'm writing these hashes of hashes of whatever in ruby and thinking.... golly i wish i was using lisp.
...
That being said, i !@#$! hate every hash/dictionary implementation i've ever encountered in a lisp or scheme.
100% writing macros to give me ruby/pythonish dictionary interactions.
If you know of a lisp that does this well PLEASE let me know.
In 1984, 40 years ago, Digital Press published the book "Common LISP: Reference Manual" by Guy L. Steele Jr. and others, more widely known as the first edition of "Common Lisp: The Language" or CLtL1. It was an early major milestone of a Lisp standardization process completed a decade later.
I'm looking for a Lisp resource I run across but can't find anymore.
It's a Common Lisp reference similar to the HyperSpec or possibly based on its text, but with a clean web design and modern HTML formatting. The name of the resource rhymes with "spec" or "hyperspec".
I just updated my Medley from the Medley Interlisp Revival project (https://interlisp.org/) to get improved CLtL2 compatibility ... and boom, CL (loop)! Now to work through some CL code I've written to see if I can get it into the environment and running. #lisp#retrocomputing
Whats a good server with cool hackers who are accepting of BDS activists? I just found out thats off topic here, with lots of ppl complaining. I 90% just post about #lisp & #scheme, but when political events involving movements im apart of crop up, I dont want to want to hold my tounge.
One more reason why it's hard to use alists as associative data structure: There is no built-in destructuring capabilities for it. It seems (ice-9 match) is no help here. Situation becomes even worse if we have a nested data structure.
Going to stack a bunch of let+assoc-ref's I guess.
The Common Lisp code in "How to Solve It in LISP" by Patrick Hall (1989) is a bit archaic.
But this work is unusual and intersting in that, unlike contemporary Lisp books, the examples don't focus just on AI but also a range of ordinary programming domains such as math, business, data structures, simulation, and more. Plus the cover is the weirdest of Lisp books.
After months, I recently returned to my fixation of utilizing beloved Python scientific libraries (numpy, matplotlib, pandas...) through a Lisp dialect. After trying Hy, EL, CL, etc., I increasingly believe that the best answer is Clojure. Very interesting is the sixth line of this code, where you can see how I calmly go to select a venv. Such user-friendliness is not at all obvious; I was surprised when I discovered I could do that so simply.