3 ms·
Common Lisp was designed by committee, and it shows. If Lisp is to become popular, it needs a good, opinionated dialect or three. Arc will probably be one of th
by Zak 19y ago
Common Lisp was designed by committee, and it shows. If Lisp is to become popular, it needs a good, opinionated dialect or three. Arc will probably be one of them. Otter may be another. It would certainly be nice if there were more libraries, but most of the things the author complains about seem to be non-problems:
>database access
Is there a problem with clsql (http://clsql.b9.com/ http://clsql.b9.com/)?
>sockets
Most Lisps (all modern ones?) support sockets. There are libraries to provide a common interface - a quick Google search got me usocket (http://www.cliki.net/usocket http://www.cliki.net/usocket)
>threads
Ok, your options are a little more limited here, but CMUCL and SBCL support threads on x86 Linux, as do Lispworks and Allegro if you want to spend money. I suspect this isn't a big problem for most people writing web apps.
>POSIX
I think this is a weak point - CL was developed at a time when there was no clear OS of the future, so it was intended to be OS-agnostic. Today's (and probably tomorrow's) world has Windows, Unix and not much else.
>a portable FFI
CFFI and UFFI both work on all the popular Lisps. What's the problem?
- ketralnis 19y agoEDIT: Sorry, I misread your comment, and mine agrees with yours rather than argues with it. But I'll leave it here for posterity :) >> POSIX >I think this is a weak point - CL [...] was intended to be OS-agnostic I don't think it's a weak point. It's OS-agnostic, which doesn't meet my needs because I need to use operating system features. Just because it wasn't built to meet my needs doesn't mean that it does.