home.social

#quicklisp — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #quicklisp, aggregated by home.social.

fetched live
  1. "If there is one thing that confuses newcomers to Common Lisp, it is the interplay of built-in CL functionality, add-ons like Quicklisp and ASDF, and what all the words mean." by Cees de Groot

    cdegroot.com/programming/commo

    #lisp #commonlisp #quicklisp #asdf

  2. 🤯 Ah yes, the riveting saga of Common Lisp packaging: where we untangle the ancient hieroglyphics of #ASDF and #Quicklisp so you can finally figure out how to install a library from the '80s. ⚙️🕰️ Because nothing screams "modern programming" like deciphering terms minted before your parents met. 📜
    cdegroot.com/programming/commo #CommonLisp #Packaging #ProgrammingHistory #ModernDevelopment #HackerNews #ngated

  3. Cees de Groot @cdegroot explains what Common Lisp library building and packaging problems ASDF and Quicklisp solve. A clear overview of these tools and what they do.

    cdegroot.com/programming/commo

    #asdf #quicklisp #CommonLisp #lisp

  4. I spent some pleasant hours yesterday hacking on my #openbsd port
    of #lem. The dependency on async-process led me to forking that
    project and making a version which will build the .so it needs if it's
    not one of the three pre-built so. I had to do the same with with the
    terminal extension in Lem itself.

    The #quicklisp and #qlot tools are new to me, and I'm learning just
    enough to be dangerous. I did run into an issue where a qlot git
    dependency will break if the top level program, lem in this case, has
    a .gitignore file. It appears that the qlot cloning will honor the
    parent gitignore.

    All of this makes me very grateful for the work done on the
    #commonlisp tooling over the last decade or so. It's also really
    apparent how much this is all a gift, from others -- because the
    community is so small. I have had to adjust my expectations, and it
    made me realize just how much I take for granted in the software
    ecosystem, and the level of polish and work I have come to feel
    entitled too.

  5. Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp. To simplify things and leverage defaults should the source tree go under ~/quicklisp/local-projects/ or ~/common-lisp/?

    #CommonLisp #quicklisp #lisp

  6. @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.

    github.com/portacle/emacsd

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

    The portacle issues should give anyone pause.

    github.com/portacle/portacle/i

    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.

  7. Finally we have got an update of Quicklisp distribution.

    A multiple Common Lisp libraries were added in this release:

    blog.quicklisp.org/2024/10/oct

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

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

  9. @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.

  10. @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

  11. @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.

    awkravchuk.itch.io/cycle-of-ev

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

    toobnix.org/w/oyrTVu3gmpXMmo7x

    #springlispgamejam2024

  12. @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 (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

  13. 📢 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 🙏

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

    #DevOps #DevX #Programming

  14. Interesting is there an implementation of the Circuit Breaker pattern for ?

    I didn't find any in the and .

    Probably I've missed something?

  15. CW: Loving Common Lisp, or the Savvy Programmer's Secret Weapon

    Mark Watson (@mark_watson) wrote this to introduce to developers who already know how to program in another language. If you are a complete beginner, you can still master the material in this book with some effort.

    leanpub.com/lovinglisp/read#le