thirteen-letters
CIEL
thirteen-letters | CIEL | |
---|---|---|
2 | 14 | |
3 | 143 | |
- | 0.7% | |
7.7 | 6.7 | |
10 months ago | 15 days ago | |
Common Lisp | Common Lisp | |
GNU Affero General Public License v3.0 | - |
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.
thirteen-letters
-
It's 2023, so of course I'm learning Common Lisp
Note that Common Lisp doesn’t require functional programming. Mutation, side effects, etc. are fine. I just write imperative code for the most part.
My code was quick and dirty, so I don’t think anyone will learn anything from it, but it’s here: https://github.com/jaredkrinke/thirteen-letters
-
Show HN: Multiplayer Word Scramble in Browser, Using Common Lisp
Thirteen Letters is a web-based, competitive word scramble game I made for the Lisp Game Jam (Spring 2023) [0].
The gameplay isn't novel, but it's a multiplayer browser game that's written in 100% Common Lisp (cf. the source code [1]). The front end uses Parenscript, Spinneret, and cl-css to translate s-expressions to JavaScript, HTML, and CSS, respectively. The back end is built using the Hunchentoot web server, Hunchensocket for WebSockets, and yason for JSON, running on SBCL.
I'm fairly new to Common Lisp, so I'm not qualified to dispense advice, but I found having a REPL on the live service to be convenient for monitoring activity, toggling settings, and fixing minor bugs on the fly. It's a lot of fun for hobby projects, although I'd be much more cautious with anything important--I definitely broke the live service a few times by not being careful! I posted a more thorough braindump elsewhere [2].
Let me know what you think! I'm happy to answer any questions. I'll play for a while, to hopefully give people a moderately worth opponent :)
[0] https://itch.io/jam/spring-lisp-game-jam-2023/rate/2103016
[1] https://github.com/jaredkrinke/thirteen-letters
[2] https://log.schemescape.com/posts/game-development/lisp-game...
CIEL
-
Writing Small CLI Programs in Common Lisp (2021)
and for CL: https://github.com/ciel-lang/CIEL/ (pre-alpha) CL with many batteries included (json, csv, http, CLI parser…) so the scripts start fast.
-
Sharpscript: Lisp for Scripting
As a CL addict, this isn't unlike Babashka: fast-starting CL scripting with batteries included. https://github.com/ciel-lang/CIEL (alpha) (otherwise the solution is to build a binary)
-
It's 2023, so of course I'm learning Common Lisp
> lots of interoperability libraries
That's true. For cases when you want to start with a good set of libraries (json, csv, databases, HTTP client, CLI args, language extensions…), I am putting up this collection together: https://github.com/ciel-lang/CIEL/ It can be used as a normal Quicklisp library, or as a core image (it then starts up instantly) or as a binary.
It can run scripts nearly instantly too (so it isn't unlike Babashka). We are ironing out the details, not at v1.0 yet.
> handling a runtime error by just fixing the broken code--in-place, without any restarts [from the blog]
Also (second shameless plug) I should have illustrated this here: https://www.youtube.com/watch?v=jBBS4FeY7XM
We run a long and intensive computation and, bad luck, we get an error in the last step. Instead of re-running everything again from zero, we get the interactive debugger, we go to the erroneous line, we compile the fixed function, we come back to the debugger, we choose a point on the stackframe to resume execution from (the last step), and we see our program pass. Hope this illustrates the feature well!
- The Embeddable Common Lisp [pdf]
-
Improving REPL experience in terminal?
check out CIEL, one of it's goal is to be a quality terminal repl
-
networking and threads
I've been doing the protohackers challenges in common lisp to learn, and I ran into a problem that is possibly a bug in the socket library, or much more likely in my misunderstanding it. At any rate the best workaround a found seems pretty ugly, so can anyone advice what would be the cleanest way to solve it, and how we're supposed to deal with sockets? The problem is basically make a tcp server, that forwards all connections to an upstream server, and does a regex find and replace on all the traffic that passes through. Here's my working solution. I haven't learned much how asdf and packages work yet, I am just using CIEL which is SBCL (2.2.9.debian) with a bunch of libraries already loaded, I think if you load usocket, usocket-server, cl-ppcre, and bordeaux-threads it should run. The program is simple, I just forward all traffic from the client to the upstream doing regex replacement on each line, and spawn a thread that handles forwarding all traffic from the upstream to the client with the regex replacement. The issue is that when the client disconnects, my program doesn't disconnect from the upstream, even when I call (close upstream) and (socket-close socket). Before closing the socket or stream, the connection shows as established in ss -tp and as belonging to the sbcl process. After calling close on the socket and stream, the connection still shows as established, just it no longer shows as belonging to the sbcl process, and tcpdump shows that the 4-way termination handshake is not sent. After killing the background thread that is also reading the same socket, the 4-way termination is sent, and the connection is closed. It seems like calling close on the stream or socket should close it? Are sockets or streams not safe to share between threads? Is there a cleaner way to handle closing the upstream connection when the client disconnects rather than calling destroy thread?
-
Common Lisp Implementations in 2023
I quite agree, so I'm making a meta-library to have useful libraries available out of the box: https://github.com/ciel-lang/CIEL/ It's CL, batteries included. You can use it as a library, as a core CL image (loads up faster), and as a binary to have a REPL, and to run scripts:
ciel --script myscript.lisp
- CIEL Is an Extended Lisp. Batteries Included
-
Babashka: GraalVM Helped Create a Scripting Environment for Clojure
No, we have to build a binary, which starts up super quickly.
I began to put together a "distribution" of useful CL libraries for everyday tasks: https://github.com/ciel-lang/CIEL/ It comes as:
- a lisp core, which you can use in your editor setup instead of sbcl or ccl, the advantage is that it loads instantly with all these libraries built-in (instead of quickloading all of them when needed)
-
Any projects want/need help?
Hi there. I'd enjoy help on anything web development for openbookstore: https://github.com/OpenBookStore/openbookstore (especially now: setting up i18n) Or, we could work on the terminal REPL experience for the CIEL meta-package: https://github.com/ciel-lang/CIEL/ We could use a better base like cl-repl or better yet, Lish.
What are some alternatives?
ql-https - HTTPS support for Quicklisp via curl
quicklisp-client - Quicklisp client.
slyblime - Interactive Lisp IDE with REPL, Inspector, Debugger and more for Sublime Text 4.
ichiran - Linguistic tools for texts in Japanese language
tools.decompiler - A decompiler for clojure, in clojure
racket-gui-easy - Declarative GUIs in Racket.
yesod-persistent - A RESTful Haskell web framework built on WAI.
arrows - Implements -> and ->> from Clojure, as well as several expansions on the idea.
CSharpRepl - A command line C# REPL with syntax highlighting – explore the language, libraries and nuget packages interactively.
cl-utils - GrammaTech Common Lisp Utilities
alive - Common Lisp Extension for VSCode
common-lisp-standard-library