3 ms·
May be you can share what Lisp image you use? I'm always open to Lisp development and see what's possible. I went through CLisp and SBCL for Windows, but deci
by ww520 16y ago
May be you can share what Lisp image you use? I'm always open to Lisp development and see what's possible.
I went through CLisp and SBCL for Windows, but decided against SBCL due to its large runtime image.
- lispm 16y agoI have the LispWorks 64bit Enterprise Edition. It does provide Unicode, concurrent threads, database access, networking, GUI lib, ... Some of the other stuff I have loaded as libraries. My base image with software loaded is probably larger than SBCL's but it also contains more stuff. LispWorks runs also nicely under Windows. Possible drawback: it is commercial and not open source.
- ww520 16y agoPossible drawback: it is commercial and not open source. I think that's the main reason. $5000 does buy a lot of libraries.
- lispm 16y agoNot only that. It buys you one of the fastest Lisp implementations, which runs nicely on Windows, Linux and Mac - everywhere with native GUI. Windows isn't that well supported by open source Lisps. The commercial ones are much better in that respect. Though, for me the Mac OS X support is more important, since I'm also not a regular Windows user.
- lelele 16y agoYes. Money buys you time.
- whyenot 16y agoYou might want to also have a look at ClozureCL for Windows[1]. It's very small and has some other nice features (OS level thread support, unicode, ...). [1] http://www.clozure.com/clozurecl.html http://www.clozure.com/clozurecl.html