@phil My personal preference is none of the Lisp-specific package managers. I use #Guix for managing all kinds of packages, including #CommonLisp. Guix also builds on ASDF, but also handles non-Lisp dependencies (mostly C libraries), which is nice.
@phil There are three layers to code management in #CommonLisp:
0. The language standard, which is very basic: you can load source code files.
1. ASDF, which manages "systems" (roughly collections of source code files, plus tests etc.) and their dependencies. If all the code you need is in your local file system, ASDF is all you need. It's also a de-facto standard, in that all modern implementations support it
2. Package managers, which download systems to the local file system.
<">
I think some people do either end up not using slime, or not using sbcl’s ext:save-lisp-and-die to save and resume their universe lisp image core when they are using slime. When you should use both.
</">
Good points.
I'll make a weaker statement.
You don't _have_ to use them.
Your mode of operation will vary.
But you must make an __informed__ decision whether to use them or not.
> As much as CL is 'standardized', it doesn't appear to have a standard way of interaction with the ecosystem.
Aside:
as a language, Common Lisp _is_ standardized, no quotes.
Yes, it is unfortunate that (official) standardization didn't get around to doing more.
Simplistically, blame it on the first AI winter.
I think most people's problem with Lisp is that it wins no popularity contests.
Like Shakespeare's Banquo from the Play, it begat kings though it was none.
#sbcl #commonLisp #slime #emacs #programming .
https://screwlisp.small-web.org/fundamental/sbcl-slime-eval-lisp-and-die/
I think some people do either end up not using slime, or not using sbcl’s ext:save-lisp-and-die to save and resume their universe lisp image core when they are using slime. When you should use both.
This article covers that.
The Common Lisp implementation of Medley Interlisp is closer to CLtL1 than ANSI but does support the condition system. The CONDITIONGRAPH tool shows the hierarchy graph of conditions.
Unfortunately the state of graphics programming frameworks in #commonlisp is not quite there yet, so it seems I'll be crawling back to #cpp and #openframeworks for my graphics needs.
Bits and pieces are there in the lisp ecosystem, but there's nothing at the moment that ties it all together in the way that oF or Processing does. In the future I might think of going down the Clojure/quill route, as it seems I should be able to leverage the full power of a lisp and all of Java/Processing.
Installing lisp for beginners.
https://screwlisp.small-web.org/fundamental/installing-lisp-etc/
So much computing is predicated on having this or a conscious alternative decision to it. Here is my attempt to help beginners get this far. What do you think?
> ANSI CL does not call for or need TCO as such.
My impression is that the ANSI committee didn't want to burden implementors by mandating tail call elimination (it is easier in Scheme), but don't take my word for it.
Besides, a stack overflow can be of great help to tackle endless loops, though that is a different story.
> DO exists because it is exactly like one common case of TCO.
Yes.
By the way, TCO as a TLA sounds like an OS/MVS thing...
@deech For the practicalities of working with #CommonLisp, the Common Lisp Cookbook is a good resource:
@ksaj @pkw @deech
oh, yeah, good book.
When I first went to read the art of the metaobject protocol and I got to where it says "if you are new to the common lisp object system, go read Sonya Keene's Object-oriented Programming in Common LISP: A Programmer's Guide to CLOS now then come back afterwards"
but I made the mistake of trying to read AMOP first (which I did not much understand or retain). #AMOP #bookstodon #commonLisp
#programming #workflow #GUI #mcclim #commonLisp #emacs #ecl #clisp #slime #leonardoCalculus #eepitch
https://screwlisp.small-web.org/lispgames/LCKR-object-oriented-simulation-simulation/
I have to say, I am really, really happy with how the flow into the thirty second GIF reflects my ideal computer useage.
Basically, I write a clim command that steers my leonardo system "like a person does" via emacs-server, visible in the background of the straightforward clim interactor GUI I generated in a couple lines.
#CommonLisp sturdy, industrial
#Scheme elegant, academic
#Emacs lisp the only actually useful lisp
#clojure if it weren't JVM-based... there's always one bad apple
#programming #gamedev #devlog #simulation #commonLisp #leonardoCalculus
https://screwlisp.small-web.org/lispgames/LCKR-a-simulation-backend-interface/
Really just a devlog! I slapped a #mcclim #gui onto my simulation so that I could click a button rather than type actions over and over again.
Then, I really just figured out that one simple-starting-arrangement idea I had doesn't work, because the only vertical move that gets triggered is from the lowest row of a tile to the highest row of the same tile.
Small "improvements".
Made some minor changes to MICRO COMMON LISP: better compatibility, pseudo-strings, more free nodes, etc.
http://t3x.org/mcl/index_d.html
#LISP #CommonLISP
#leonardoCalculus #Sandewall #programming #objectOriented #simulation #lisp #commonLisp
I feel like this article is one of those moments that is a monumental achievement for the writer themselves, but precedes adding glitzy picture making (which will eventually come too).
If you remember, I was recapitulating my somewhat failed #lispgamejam #gamedev . This time and in about half a week just now - I got the plant/insect/bird Breitenbergian Vehicle simulation workin'.
https://screwlisp.small-web.org/lispgames/LCKR-completing-the-simulation/
Planning to write a post on #CommonLisp #REPL customization. Gathering state-of-the-art customizations. Remembered that I implemented native graphical debugger in #Nyxt once (immortalized in Ndebug https://github.com/atlas-engineer/ndebug). Went to check on the current state of Nyxt-native debugging.
And yes, native debugger was removed too, much like many other signature features. Which might be a reason to hold a grudge about my work being erased, I guess?
But I'm more saddened about this exemplary REPL hacking piece gone missing, really. I want to point at good examples of custom REPLs in my new post... and there aren't many anymore 
Yay! Last-minute success! (only for left-to-right rendering, though)
It appears like I have the scaling working correctly and SDF fonts are rendering as expected. It's even working pretty nicely with the text sizing demo! It looks like I still have a bug with the text bounding box but, visually things are looking much better.
#hackThePlanet
#lispyGopherClimate #interview with 500 hats of @lambdacalculus
Their kofi: https://ko-fi.com/lambdacalculus
https://communitymedia.video/w/iEzEkc2SPuL5twaSnTEEq5 #archive
of #DOOM #redstaros #piratebox fame
Previewing their
#phreakNIC #technology #hacker
#HOPE #HOPE_16
talks!
Also #oldComputerChallenge happening RIGHT NOW https://screwlisp.small-web.org/occ/25/jul15.txt (I'm doing #xemacs emacs)
LambdaCalculus knows #emacs #lisp ...! And that's where it began then #commonLisp #CCL on the #macintosh
