LispWorks or SBCL or what?

I don't care about ^GNU/_Freedom, which should I use?

SBCL because LispWorks is ^non-_free.

>>2
SBCL is not GPL either, Rimmis

>>3
GPL or not, the more important matter is freedom. GPL is merely one licence out of any number of possibilities that provide freedom.

SBCL, Slime, Clisp or Lispworks.

>>5
Slime is just a birdge between Emacs and whatever lisp implementation.
>>1
Myself, I prefer SBCL since the source is in public domain, but LispWorks itself is not bad, especially if you want to develop commercial stuff as it has a lot of libraries and excellent documentation. If you want to look into other commercial Lisps, check out Allegro CL (*nix and Win), Corman (Windows exclusive), Scieneer CL(*nix exclusive). Myself, I'm mostly fine with using SBCL, ClozureCL and ECL - they work almost everywhere, and it's not hard to keep code portable between them. GNU CLisp is okay, but it tends to be my last choice. I've also tried the Allegro and LispWorks - they were quite nice to use, especially when it comes to some of the libraries (and documentation) they offer (such as GUI-related stuff). Allegro and LispWorks also provide an IDE, which you might like, but personally I prefer Emacs+SLIME+Paredit+Redshank a lot more, and can do the same things you can do in the IDE and more. If you dislike using Emacs, be sure to check out their IDE.

SBCL (Steel Banks Common Lisp) does not have a windows port. Also it is based on CMUCL (Carnigie Mellon University Common Lisp). The reason its called Steel Banks is that Mellon was a banker and Carnigie was into Steel.

CLisp has a windows port. And there is Lispbox which integrates Lisp with emacs and slime
http://common-lisp.net/project/lispbox/

>>7
Stop talking about things you don't know about.
I've used SBCL on Win32 for a year and a half now. The Windows port works just fine: http://sbcl.sourceforge.net/platform-table.html
The Windows port is not as perfect as the Linux port, in that the threading is not supported and unix signals are a bit broken, but if you can't wait for official threading/signal support on Windows, there are some experimental forks which provide that.
Even if you didn't want to use SBCL for some strange reason, CLisp is still hardly the best choice you could pick. On Windows, the most complete free choice is ClozureCL which has both threading at 64bit support (as well as native compilation, of course).
Also, Lispbox is severly outdated (old CLisp, ancient SLIME, etc). Just grab everything from SVN and enjoy latest SBCL or CCL, SLIME, Emacs/Paredit/... It's not even hard to build it yourself.

>>8
Some people use a toy operating system when programming in their toy languages; now they have two problems.

11 Name: Anonymous 2011-02-04 19:34

<