@hairylarry

I respect your adventure.

It's unfortunate that people are still using portacle.
It's 8 years old. It's #emacs build is not current, the build flags are ancient!

The packages do work, but there have been improvements in the last 8 years.

The emacs config is here. Crufty.
Slime, Company, Magit, Paredit and Ag.

https://github.com/portacle/emacsd

Common lisp, #sbcl and #quicklisp are not difficult to install.

The portacle issues should give anyone pause.

https://github.com/portacle/portacle/issues

Portacle doesn't do that much. I think it would be better to install things yourself so you know what you have and avoid the cruft.

My experience may give me a bad POV.

@jackdaniel is the current #quicklisp release of #mcclim good?

Finally we have got an update of Quicklisp distribution.

A multiple Common Lisp libraries were added in this release:

http://blog.quicklisp.org/2024/10/october-2024-quicklisp-dist-update-now.html

Please read the list and send in the comments the 3 lisp libraries that you consider the most interesting!

#commonlisp #quicklisp #update

#Quicklisp contains 2160 "projects" comprising 5500 systems and 7_101_546 lines of #CommonLisp code. (Only .lisp files counted.)

(Based on my quick and dirty assessment.)

There's finally a new Quicklisp dist after literally a year, even though there's no post on the Quicklisp blog #Quicklisp #CommonLisp #Lisp

Is #Quicklisp still maintained? #Lisp

#Quicklisp's design does not require that the transitive closure of the project dependency relation be a DAG, and indeed, there are several circular dependencies. This mostly occurs because of test systems.

Older versions of clnix tried to explicitly support building multiple projects together to avoid the circular dependencies. However, there's a huge circularity containing many commonly-used packages.
https://git.sr.ht/~remexre/clnix/tree/58c27023c01341f23b5d57da2be70a07c7135e66/item/quicklisp/overrides.nix#L7

@undltd Still in the early setup phase, so a bit hard to tell... But will keep you posted! Right now I have a problem getting the sly connection working. When I connect to the sly-repl from emacs I get an error about #quicklisp not being available on my system, although it works when I start up #sbcl inside emacs.

@louis what have you been thinking about doing-instead-of- #quicklisp #lisp? Now I have the context of game, or game-cartridge development and distribution as a key problem, I guess I have to tangle with this.
Options seem:
1. Upload and download built blobs to and from itch.io (?!?!)
2. Use quicklisp with your own package source
3. Make Makefiles, rely on packagers to package you hypothetically.

But I think we are actually encountering the universal vs modular knowledge source problem domain

@awkravchuk
Hey, I didn't manage to install your game because openbsd's current allegro port is still 4.2. Could we talk about doing something like a formal specification for a Common Lisp Software Game Console in the future.

https://awkravchuk.itch.io/cycle-of-evil

I get through some parts of the #quicklisp build at least!

https://toobnix.org/w/oyrTVu3gmpXMmo7xiWiqYZ

#springlispgamejam2024

Live - Cycle Of Evil Fail To Build, Lisp popularity retrospective - 5/30/2024, 10:13:18 PM

https://toobnix.org/videos/watch/b6b0cf45-2e99-4e7d-b091-6c24595610b1

https://toobnix.org/w/khxRivsFVFkpQKBAWvM2ek

#Inaugural #toobnix
#howTo #lisp #commonLisp #sbcl #quicklisp #McCLIM #openbsd #video #gameDevAdjacent
in so many words. Five relaxed minutes.

The rest of this week is going to be loosely #springlispgamejam2024 live->videos on here.

Thanks https://sdf.org

Follow @screwtape_channel

@screwtape @sjl

A few thoughts on your comments:

➡️ I consider emphasizing the trivial stuff a good move for an introductory article.

➡️ When the article was written (2018) the Naughty Dog engine existed but had its own variant of #Lisp (GOAL - Game Oriented Assembly Lisp). Not sure that should be mentioned in the article.

➡️ The article attempts to provide tools to discover and use exiting libraries (#quicklisp)

The article is from 2018. Back then

📢 Looking to simplify your #Docker setup? Give #bdockerimg a try!

✔️ Starting collection of pre-built images for niche tools (#bmakelib, #QuickLisp & #SDKMAN)
✔️ Basic tests to ensure things work
✔️ Help me grow the collection! Request new images or submit PRs 🙏

👀 https://github.com/bahmanm/bdockerimg - the logo is the most creative work I've ever done 😂
🗣️ https://matrix.to/#/#bdockerimg:matrix.org

#DevOps #DevX #Programming

@alanz It would be great to port all the #quicklisp packages collection to #guix! I lost myself in the packaging Trial (#Kandria 's game engine and #pgloader a few years ago.

Is someone using #quicklisp? I searched for a package in quickdocs.org but got a 404.
I read that some projects choose #commonlisp at first, then migrate to #nodejs or #python for the number of available libraries.
Maybe I should find out myself and give #commonlisp a chance.

#Quicklisp update! http://blog.quicklisp.org/2023/10/october-2023-quicklisp-dist-update-now.html

#Lisp

Interesting is there an implementation of the Circuit Breaker pattern for #commonlisp?

I didn't find any in the #Quicklisp and #Github.

Probably I've missed something?

@louis Personally I've long since moved to #Guix.

#Quicklisp's disregard for security makes it no friend of mine.