4 ms·
Thanks, that was a fun read. BTW, I don’t think Richard totally dislikes Common Lisp: years ago I got an email from him about releasing my ancient Springer-Verl
by mark_l_watson 8y ago
Thanks, that was a fun read. BTW, I don’t think Richard totally dislikes Common Lisp: years ago I got an email from him about releasing my ancient Springer-Verlag Common Lisp book under the FSF documentation license. Unfortunately I couldn’t do it because I didn’t have the manuscript files.
- avar 8y agoIf you own the copyright to the text couldn't you make it known that if someone were to OCR it, clean up the formatting, and publish it that the result could be freely distributed?
- jacobush 8y agoI guess in a fair and honest world, yes because it's legal? But in our actual world, it's also legal but publishers may play dirty and somehow claim rights because you published something based on their edition? Just thinking out loud.
- lispm 8y ago> I don’t think Richard totally dislikes Common Lisp maybe not totally, but mostly. Beyond that he does not care about it and isn't interested in it.
- kazinator 8y agoIf you were already an "advanced Lisper" in the 1980's, Common Lisp might be something like C11 to someone who had expert C chops before even C99. I code in C regularly, yet I do not care and am not interested in C after C90. Only some library features of C99 and that's about it. Stallman's concepts of what is Lisp, how to use Lisp, how to implement Lisp, were formed long before Common Lisp. If you're in that position, it's easy to have allergic reactions to requirements you don't agree with.
- lispm 8y agoKind of surprising, since Stallman was a developer with and user of Lisp Machine Lisp, the single biggest influence of Common Lisp. Maclisp and its successor Lisp Machine Lisp, were probably his biggest influences. Emacs Lisp is based on Maclisp - without the features of Lisp Machine Lisp like keyword arguments, Flavors as the object-system, ...
- fusiongyro 8y ago"Common Lisp Modules" by any chance?