Top 23 Common Lisp common-lisp Projects
-
Project mention: Are there extensible environments in the manner of Emacs outside of text editors and developer tools generally? | reddit.com/r/lisp | 2021-04-04
Nyxt fits in there.
-
pgloader https://github.com/dimitri/pgloader
-
Scout APM
Scout APM - Leading-edge performance monitoring starting at $39/month. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
From the code https://github.com/slime/slime/blob/68c58c0194ff03cd147fcec99f0ee90ba9178875/slime.el#L120, it looks like the correct name would be slime-lisp-mode-hook .
-
Common Lisp itself has Roswell, which I am disappointed to see is not even mentioned in the article.
-
-
sketch
A Common Lisp framework for the creation of electronic art, visual design, game prototyping, game making, computer graphics, exploration of human-computer interaction, and more.
-
Project mention: Are there extensible environments in the manner of Emacs outside of text editors and developer tools generally? | reddit.com/r/emacs | 2021-04-03
Well, there is Lem, the editor built for out-of-the-box support for Common Lisp: https://github.com/lem-project/lem
-
-
My current wtf moment with trying to use CL: https://github.com/Clozure/ccl/issues/311
-
Project mention: Lisp Implementations similiar to old Lisp Machines? | reddit.com/r/lisp | 2021-02-11
But I don't want to have a net negative contribution to this thread, so I'd also recommend looking at some of the McCLIM applications, including the inspector Clouseau, editor Climacs and the CLIM interactor, which are very much Lisp machine-inspired.
-
Speaking about Common Lisp, the only commercial-level compiler implementation that I know of is https://github.com/rigetti/quilc by /u/stylewarning et al.
-
Python
-
> After much deliberation, the Python Steering Council is happy to announce that we have chosen to accept PEP 634, and its companion PEPs 635 and 636, collectively known as the Pattern Matching PEPs
This is why I'm still enamored with Lisp. One doesn't wait around for the high priests to descent from their lofty towers of much deep pontification and debate with shiny, gold tablets inscribed with how the PEPs may be, on behalf of the plebes. One just adds new language feature themselves, eg. pattern matching[1] and software transactional memory[2].
-
-
There's also Ulubis and Paulownia. The latter is not really usable yet from what I understand, but I've not had much luck with Ulubis either.
-
Project mention: Idiomatic way to handle non GC objects, i.e. OpenGL textures ? | reddit.com/r/Common_Lisp | 2021-04-16
A good way to do it is to keep a staging area of sorts that keeps track of the manually allocated objects and their state. When you allocate you batch all objects to allocate together and then execute the load in one go, updating the records in the staging area. Then, when you're ready to switch to a different scene or whatever, you diff the staging area against the current set of objects that need to be live and deallocate everything else in one go.
-
Project mention: Check if a string is a member of a list of strings | reddit.com/r/learnlisp | 2021-03-31
If you are used to the str library:
-
-
abcl
Armed Bear Common Lisp <git+https://github.com/armedbear/abcl/> <--> <svn+https://abcl.org/svn> Bridge
Project mention: Paul Graham recounts his work on Lisp and other things | reddit.com/r/lisp | 2021-02-17Ashwin Ram's "An Ode to the Growth of Programs" https://github.com/armedbear/abcl/commit/d58dd55fc1abd9777b53fa9bc2dc5d349ab231b7
-
Project mention: Python Programming and Numerical Methods: A Guide for Engineers and Scientists | news.ycombinator.com | 2021-02-17
I guess my number one piece of advice is to estimate time accordingly. Most things can be solved using pre-existing solutions with a bit of work, if you’re patient and you can afford to put in the time to do it.
Secondary to that:
- Learn to use FFI very well try hard to find libraries written in C.
- Familiarize yourself with the structure of LAPACK and what it offers.
- Learn to use a profiler and debugger (if using Lisp: SB-SPROF, TIME, SLIME, and SLDB).
- (if using Lisp) Contribute useful things back to existing libraries, like MAGICL [0].
Maybe it’s not the best analogy, but scientific programming in Lisp is currently like woodworking (compared to building IKEA with Python).
-
Project mention: Consfigurator -- Lisp declarative configuration management system | reddit.com/r/lisp | 2021-03-11
Nice! It reminds me of Adams which shares similar goals: https://github.com/cl-adams/adams
-
Project mention: [SBCL] Generating a binary of a GUI built with Sketch | reddit.com/r/lisp | 2021-04-17
If all else fails, I recommend trying to contact author through creating an issue on github. If that fails too and you are too tired to continue that fight, have a look at trivial-gamekit (beware: shameful self-plug).
-
Here's an example from my codebase which uses a lot of creative naming. There are "suffixes" (which I guess is a grammar term) but also "patches", "penalties", "synergies", "segfilters" and so on which are the terms I made up solely for this code.
Index
What are some of the best open-source common-lisp projects in Common Lisp? This list will help you:
Project | Stars | |
---|---|---|
1 | nyxt | 5,727 |
2 | pgloader | 3,353 |
3 | slime | 1,427 |
4 | roswell | 1,331 |
5 | sbcl | 1,310 |
6 | sketch | 1,030 |
7 | lem | 906 |
8 | sly | 776 |
9 | ccl | 588 |
10 | McCLIM | 464 |
11 | quilc | 338 |
12 | CLPython | 316 |
13 | trivia | 213 |
14 | coalton | 204 |
15 | ulubis | 193 |
16 | trial | 182 |
17 | cl-str | 181 |
18 | mito | 179 |
19 | abcl | 153 |
20 | magicl | 140 |
21 | adams | 137 |
22 | trivial-gamekit | 131 |
23 | ichiran | 123 |