5 ms·

Adding my own disagreement about using either portacle or roswell. If you're running literally any widely used Linux distro, or {Free|Open}bsd you are a package

Adding my own disagreement about using either portacle or roswell. If you're running literally any widely used Linux distro, or {Free|Open}bsd you are a package install away from a working common lisp install. I've seen this come up alot in irc and reddit, this push to get people to use a C library (!) to get to common lisp, and its downright bizarre. If you're that bent on packaging and C, use Guile or Gambit. And if you're just a random person perusing this thread, just go download the simplest thing and get started, not slime (which is awesome) not Lem (which is fine), just lisp and a text editor

snazz 7y ago
Yes. A detail that I found quite amusing about Roswell was that it segfaults on OpenBSD; the problem could have been altogether avoided by writing it in Lisp. I had to dismiss Lem because it seemed to depend on Roswell and Roswell was not going to cooperate. The entire point of Common Lisp is to make stuff work across implementations. You shouldn’t need to test five implementations on your development machine. The only time I can see something like Roswell (but not in its current form) being useful is an automated CI tool, but even then it isn’t really necessary.
- dtornabene 7y ago
  So, due to someone taking the time on irc, I managed to get Lem installed on a box at some point recently sans roswell. It doesn't actually depend directly on it, though I think there are some things built on Lem that use roswell.
p_l 7y ago
The problem is that for years distro-bundled Common Lisp was broken thanks to well meaning efforts in Debian. I'm speaking of "common-lisp-controller". Which led to some problems that made avoiding distro packaging the norm.
- dtornabene 7y ago
  Yeah, people have and had problems with common-lisp-controller, I certainly have. That being said I'm not one to turn to the arms of C to solve an environmental problem, not when it can be done correctly, if with effort, from the host language itself
deleted 7y ago
[deleted]

snazz 7y ago

Yes. A detail that I found quite amusing about Roswell was that it segfaults on OpenBSD; the problem could have been altogether avoided by writing it in Lisp. I had to dismiss Lem because it seemed to depend on Roswell and Roswell was not going to cooperate. The entire point of Common Lisp is to make stuff work across implementations. You shouldn’t need to test five implementations on your development machine. The only time I can see something like Roswell (but not in its current form) being useful is an automated CI tool, but even then it isn’t really necessary.

dtornabene 7y ago
So, due to someone taking the time on irc, I managed to get Lem installed on a box at some point recently sans roswell. It doesn't actually depend directly on it, though I think there are some things built on Lem that use roswell.

p_l 7y ago

The problem is that for years distro-bundled Common Lisp was broken thanks to well meaning efforts in Debian. I'm speaking of "common-lisp-controller". Which led to some problems that made avoiding distro packaging the norm.

dtornabene 7y ago
Yeah, people have and had problems with common-lisp-controller, I certainly have. That being said I'm not one to turn to the arms of C to solve an environmental problem, not when it can be done correctly, if with effort, from the host language itself

deleted 7y ago

[deleted]