Sunday, December 18, 2005
New Year's Resolution
Regular backups.
Also, thank Apple for putting 'terminal' on the install disk.
Thank you. That is all.
Also, thank Apple for putting 'terminal' on the install disk.
Thank you. That is all.
Thursday, December 08, 2005
Portable Allegroserve as a de facto standard?
The "Ruby as an acceptable Lisp" and Reddit discussions (I don't really need to supply links, do I?) brought back to the surface a question I ask myself often.
It's true that Common Lisp doesn't have multithreading or network clients in the standard, and people want that, but what's wrong with Portable Allegroserve? The acl-compat component has those covered (if the underlying implementation has support) for Allegro, LispWorks, CMUCL, SBCL, OpenMCL, SCL, Corman, CLisp. It appears to be used a lot, and has decent documentation.
Why not just use that and move on to the next problem? Is there something horrible about Portable Allegroserve I should know about?
It's true that Common Lisp doesn't have multithreading or network clients in the standard, and people want that, but what's wrong with Portable Allegroserve? The acl-compat component has those covered (if the underlying implementation has support) for Allegro, LispWorks, CMUCL, SBCL, OpenMCL, SCL, Corman, CLisp. It appears to be used a lot, and has decent documentation.
Why not just use that and move on to the next problem? Is there something horrible about Portable Allegroserve I should know about?