I don't see these issues mentioned by anyone else which is bizarre to me. I don't think there are any valid reasons to continue to use sourceforge today, so why such an important project continues to use it confuses me a lot. I think not supporting encryption or authentication for something as important as fetching source code makes QL a non-starter for me and hopefully for anyone else who cares about security.Īnother issue I have ran into, is that SBCL is hosted on sourceforge, which has in the past injected malware into projects downloadable archives! I consider this to also be a security issue, and sourceforge in general is not pleasant to work with. Last time I checked on it, QuickLisp doesn't support fetching packages over anything except for plain http, with no encryption and no verification mechanism in place to detect files that may have been tampered with during transmission.
I'm sure there are more pros/cons, but that's what came to mind just now. * I really, really wish SBCL could support fully static builds, to enable distributing binaries to non-glibc Linux distributions * Since the language itself is frozen in time, you need lots of interoperability libraries for threads, synchronization, command line arguments, and tons of other things * The most popular package manager (QuickLisp) is nice, but not nearly as featureful as I've become accustomed to with newer languages/ecosystems * Even as an Emacs noob, the integration with Common Lisp is excellent, and it works great even on my super slow netbook where I've been developing - this isn't as big of an advantage these days with fast computers, VS Code, and language servers, but it's definitely retrofuturistic * Common Lisp has a lot of implementations and there's a good deal of interoperability - I was able to swap out implementations to trade speed (SBCL) for memory usage (CLISP) in one case (multiple compatible implementations is one of the reasons I've been leaning towards CL instead of Scheme for learning a Lisp) * REPL-driven programming is handy in situations where you don't quite know what will happen and don't want to lose context - for example parsing data from a source you're unfamiliar with, you can just update your code and continue on instead of having to save, possibly compile, and restart from the very beginning
* The condition system is neat and I've never used anything like it - you can easily control code from afar with restarts
Here's what I've liked about Common Lisp so far: Wow, wasn't expecting to see my post on here! Eventually, I want to write a follow-up, but I'm still a beginner.
0 kommentar(er)
