codyreichert / awesome-cl Goto Github PK

Hi !
Plump is in the XML category, but it's a html/xml parser, tolerant on malformed markup. So it could be in the web category, where is its cousin lquery which plays nice with it (also with CLSS), so having both or the three side to side could be nice.
Or maybe move XML just below Web.
Saying that because it would have saved me time.

Cheers !

The URL for Ironclad in awesome-cl is http://method-combination.net/lisp/ironclad/ (Ironclad v0.32) which is outdated.

Ironclad is currently maintained at https://github.com/sharplispers/ironclad (Ironclad v0.37).

Just wanted to create an issue for some currently broken links (the reason the Assertible badge is red). I should be able to knock these out later today, but wanted to document:

• 404: https://addons.mozilla.org/de/firefox/addon/beautify-practical-common-lisp/?src=search
• 404: http://emergent-languages.org/Babel2/
• server error (50x): http://unlicense.org/

@vindarel thanks for keeping on top of everything, I haven't been able to spend much time here as I'd like, but I'm getting caught up. I appreciate the help!

Parenscript has been moved to https://common-lisp.net/project/parenscript/, GitHub repository is archived and marked for deletion, per note in the description at https://github.com/vsedach/Parenscript (link provided in the list):

MOVED TO C-L.NET GITLAB. THIS REPOSITORY WILL BE DELETED

https://filonenko-mikhail.github.io/cl-portaudio/

Well documented, and easy to use. Works great with SBCL under Windows, Linux and macOS

Seems useful and general enough: https://github.com/Shinmera/definitions

No reason to point people at the google code archive: https://github.com/wmannis/cl-svg

I think to know which application is awesome, is to look at

• Monthly Quicklisp download stats
• ASD files of CL prject. see what library they use. (but I think the first point already enough)

Hi,
I think you can add this precious resource.

MIT 6.001 course - Structure and Interpretation of Computer Programs

Saw this one pop up, but I wasn't able to find where it moved to:

404: https://github.com/ysz/screamer-plus

Maybe it moved to gitlab or notabug -- just making a note here to remember to look at it.

Hello!

i think the URL of cl-i18n points to the old, unmaintained, version of the library; the new repository is:

https://notabug.org/cage/cl-i18n

Thank you for your awesome work! :)
Bye.
C.

Varjo - Lisp to GLSL translator. Not available on Quicklisp. LLGPL.
It is in quicklisp and its licensed under 2 clause bsd

This list is about libraries. Would that make sense to add a "Software" or "[Open Source] Projects" section ? I'd like a place to reference example CL software, like does lisp-lang, but a real list, to put projects like Potato, Turtl, pgloader (already in this list), and even example websites if I find some… (apart quickdocs).

Sycamore
A fast, purely functional data structure library in Common Lisp.

either this fork https://github.com/40ants/cl-telegram-bot or the original if it accepts PRs.

This program uses CLOS. It renders a postscript file of a musical score that can then be converted to a pdf.
It is also one of slippery chicken's music notation backends in addition to lilypond and musicxml.
A wikipedia entry for the program can be found here.
The program's manual and documentation can be found here

Ironclad is generally considered unsuitable for cryptography (but is still very useful for the message-digest functions), so perhaps a comment should be put in there?

The http-parse ("An HTTP parser in Common Lisp") package has been put under the "Parsing html" section, but it's a library to parse HTTP requests/responses, and not HTML.

In the same section, there are two typos in the description of Plump - "A lenient HTTP/XML parser, tolerand on malformed markup" should be s/HTTP/HTML/ and s/tolerand/tolerant/.

[OBSOLETE] Make Common Lisp shell-friendly

https://github.com/fukamachi/shelly

Iterate is currently noted as having 'no license specified', whereas the file iterate.lisp is MIT-licensed -
https://gitlab.common-lisp.net/iterate/iterate/-/blob/master/iterate.lisp

A few implementations are missing any links for descriptions of how well they comply with the ANSI Common Lisp standard. Any help locating such would be awesome.

I saw you listed PORTACLE (which is pretty cool btw) I have a similar project as a docker container

https://github.com/listp/lisp-machine
https://listp.github.io/blog/2016/12/29/a-lisp-machine-in-docker/ (write up)

https://github.com/svspire/time-parser

Based on very limited research, it looks like http://codys.club/awesome-cl/ (redirected from http://codyreichert.github.io/awesome-cl) might be generated from the gh-pages branch: https://github.com/CodyReichert/awesome-cl/tree/gh-pages

It seems that that branch was last updated 8 months ago, which might in turn mean that http://codys.club/awesome-cl/ might be pretty stale and might be due to an update?

I wish there was an easy way of ascertaining on what date the site was last updated.

I think someone should look into this. Sorry if I made any incorrect assumptions.

Casting SPELs in LISP - http://www.lisperati.com/casting.html

The Land of LISP - http://landoflisp.com

An awesome online tutorial and book that are not listed yet.

GitHub: https://github.com/hawkir/calispel

I believe it provides a couple of procedures that lparallel misses, e.g. the "select" procedure to choose the next available channel among a set of channels.

I don't know of any, and would love some suggestions.

IT field changes very quickly. Some package that used to load with (ql:quickload :some-package) may not work any longer. How do you regularly review the correctness of the presented information? Do you rely on new issues? Would it be possible to set up virtual machines with Linux and Windows and run some tests that verify that the packages suggested there at least do install successfully?

Hello, I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request.

It is currently being used by

• https://github.com/vsouza/awesome-ios
• https://github.com/matteocrippa/awesome-swift
• https://github.com/dkhamsing/open-source-ios-apps

Examples

• https://travis-ci.org/matteocrippa/awesome-swift/builds/96526196 ok ✅
• https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/95754715 dupe 🔴

If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project.

See https://github.com/dkhamsing/awesome_bot for options, more information
Feel free to leave a comment 😄

Hello,

seems to me that the repo on notabug is not in sync with the one here.

Also the fact that you can submit PR and issues both here and there may generate confusion.

Hope this helps.
Bye.
C.

add in Natural Language Processing list:

http://emergent-languages.org/Babel2/

Good idea from this discussion https://www.reddit.com/r/lisp/comments/9iq8dc/what_happened_to_the_common_lisp_foundation/

Perhaps there should be a way to visually mark popular things on a list so it's obvious that e.g. bordeaux-threads is on top of a list because it's so widely used, not just because it's first alphabetically. It would also make which categories need revisiting more obvious.

I suggest a simple 👍 (https://unicode-table.com/en/1F44D/ ) before the library name:

• 👍 ASDF - Another System Definition Facility; a build system for Common Lisp. Expat.

(If it's too ugly, maybe community standard:

• ASDF - Another System Definition Facility; a build system for Common Lisp. Expat. community standard.
  )

But, we have to stress in the contributing guidelines (see the new pending PR) that our goal is not to list every defacto/popular libraries.
When there is a "conflict", it would be useful to name the most popular lib anyway, if only to show that this section was curated. We could do like I did with Dexador:

• Dexador - An HTTP client, that aims at replacing Drakma. MIT.

citing Drakma on the same line, afterwards.

It appears that some of your suggestions will not work on Windows. Although it is in theory possible to make it work on Windows though MSYS2 or similar, often it is not worth the trouble. For a brief moment, I had Qtools working on Windows perfectly, but after the recent big update or my changes, it seems impossible to make it work again. With the other contender namely, cl-cffi-gtk I had even less luck.

Feb 2018 download statistics suggest split-sequence is quite popular; and therefore, perhaps, deserves a mention here - but not sure where it should go (perhaps, Data Structures), or whether it should be labelled as defacto.

Edit: Or is this subsumed by quickutil?

Current address is: https://common-lisp.net/project/ecl/

Lisp for the Web is a book about making a web application. The author is Adam Tornhill. The book demonstrates how to use Hunchentoot, parenscript, cl-who, and cl-mongo.

https://leanpub.com/lispweb

http://minispec.org/index.html is down.

Links that use the [A Link](123) notation are leading to the wrong address like:

Https://github.com/CodyReichert/awesome-cl/blob/master/123

clack requires a server such as hunchentoot or woo; it is a wrapper around such servers and does not replace hunchentoot.

https://github.com/svspire/cl-simpledoc

Reminder for https://gitlab.common-lisp.net/clpm/clpm

The optima is archived for a long time.

Instead trivia is still in active development.

Also it is compatible with optima. Is there any reason that we do not make trivia the default recommendation?

I failed to mention this on the official project page (this has since been rectified), but Universal-Config has been superseded by Ubiquitous. If you could link to that instead, it would be much appreciated.

A reminder to add https://github.com/borodust/claw now or in a bit.

The link to the package for underneath iterate gives a 404 not found error

I am not massively knowledgeable about the Common Lisp library and tool-space, and would love suggestions of all sorts.

Today I am reminded of the existence of https://common-lisp.net/project/elephant/
Is it awesome? I wasn't sure if it is i'll add it and make a pull request.

When google/lisp-koans#111 is merged, I think that the Lisp Koans should be added as a learning resource.

Actually Practical Common Lisp is also online
http://www.gigamonkeys.com/book/