| drracket | cl21 | |
|---|---|---|
| 4 | 2 | |
| 442 | 901 | |
| 0.7% | 0.0% | |
| 7.7 | 0.0 | |
| 8 days ago | almost 3 years ago | |
| Racket | Common Lisp | |
| GNU General Public License v3.0 or later | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
drracket
-
DrRacket 8.7 crashes to desktop on Windows...does anybody know how to prevent these?
I've filed a bug report on Github: https://github.com/racket/drracket/issues/596
-
Emacs-like editors written in Common Lisp
The original version of DrRacket was written in C, but it has been rewritten in Racket a long time ago. https://github.com/racket/drracket
I use a mix of DrRacket, WinEdt and Geany (with more color in the matched parenthesis).
- Racket->Rhombus: To Sexp or not to Sexp?
-
What language for an IDE
To be fair, I'm not exactly sure which parts of emacs are written in C, but all extensions which make it more than an editor (i.e. an IDE) are interpreted lisp. Still, I'm not convinced. Another example, DrRacket, the IDE for Racket is written entirely in Racket, and that's plenty fast as far as I can tell*. It's a bit slow to start up, but that's all Racket programs.
cl21
-
Emacs-like editors written in Common Lisp
> And Lisp is almost uniquely able to handle transitions to later standards as I described above. You don't actually have to forfeit backwards compatibility entirely or at all if the changes are handled by moving to a new default base package. :cl-user/:cl become :cl##-user/:cl##
Go use cl21[0] if you care for this sort of thing.
> more generic functions would open up more interesting developments later
generic-cl[1]. But in a prefix-oriented language, I just don't see this as particularly important.
> you don't necessarily want to bless a particular concurrency model
You do[2]; this is one of the notable deficiencies in the cl standard that really bites, today. It is being worked on.
0. http://cl21.org/
1. https://github.com/alex-gutev/generic-cl
2. https://www.hpl.hp.com/techreports/2004/HPL-2004-209.pdf
-
Why are the makunbound functions fmakunbound, makunbound, and slot-makunbound named this way?
Dropping the idea for a new CL standard, adding these to CL21 would be the next option (I don't think such changes fit the spirit of radical-utilities).
What are some alternatives?
generic-cl - Generic function interface to standard Common Lisp functions
racket-lang-org
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
egui - egui: an easy-to-use immediate mode GUI in Rust that runs on both web and native
vscode-ripgrep - For consuming the ripgrep binary from microsoft/ripgrep-prebuilt in a Node project
cl-lsp - An implementation of the Language Server Protocol for Common Lisp
Kawa
math
gui
githut - Github Language Statistics
Carp - A statically typed lisp, without a GC, for real-time applications.
typed-racket - Typed Racket