usocket VS cl-sml

I learned from usocket. And I wrote mine here

How about starting with the USOCKET library?

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 is this?

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.