usocket | cl-sml | |
---|---|---|
2 | 3 | |
211 | - | |
0.5% | - | |
6.5 | - | |
about 2 months ago | - | |
Common Lisp | ||
GNU General Public License v3.0 or later | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
usocket
Posts with mentions or reviews of usocket.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-17.
-
How to Write ASDF Tests?
I learned from usocket. And I wrote mine here
-
Writing netcat with Lisp
How about starting with the USOCKET library?
cl-sml
Posts with mentions or reviews of cl-sml.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-21.
-
Is There a Way to Make Two ASDF Systems Interdependant?
I am have a library that initially was being developed to mainly focus on working with kernels, but as I found myself needing more support code I ended up adding a lot of features to this library such as string manipulation and logging. I am now working on removing the excess feature code to keep my library focused on one thing and one thing only. I was able to easily remove my string manipulation code into a new library called cl-sml, but I am running into nothing but trouble with removing my logging code. See, my logging code depends on some of the code in this library and I would basically need to copy a third of the codebase in order to make the logging code work... and even then it would not work as desired because certain global values would then be using the versions from the logging library instead of the versions from the os library. I would really rather not bloat either library. What I want to do is have my logging library use the following from the os library:
-
How to Write ASDF Tests?
How is this?
-
How Am I Triggering SBCL's Stack Guard?
I fixed a lot of the issues you were talking about and stress tested, but this is still a library in a VERY VERY beta testing state and by no means should be being used for anything yet (I am just starting to write tests now). You can see it here if interested, but again I still wouldn't use it as I may change things soon.
What are some alternatives?
When comparing usocket and cl-sml you can also consider the following projects:
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.
cl-os
roswell - intended to be a launcher for a major lisp environment that just works.
core-project-org
nyxt - Nyxt - the hacker's browser.
Github-API-CL - Common Lisp Github REST API Client
sbcl - Mirror of Steel Bank Common Lisp (SBCL)'s official repository
cl-sll
clasp - clasp Common Lisp environment
pgloader - Migrate to PostgreSQL in a single command!