Re: How Common Lisp sucks
- From: Friedrich Dominicus <just-for-news-frido@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 18 Apr 2006 07:54:13 +0200
Ron Garret <rNOSPAMon@xxxxxxxxxxx> writes:
Very funny, I don't know of any standardization in C about Sockets,
1. CL lacks standardized support for many operations that are
necessities in today's world (e.g. sockets, database connectivity,
foreign functions). Moreover, it lacks any mechanism by which these
features could be standardized. It is claimed that there are portable
libraries that work across implementations that provide de facto
standards, e.g. UFFI, but these claims are false. I don't have time to
get into details at the moment, but the fact of the matter is that
trying to use Lisp for e.g. writing a Web server is an incredibly
painful experience compared to doing the same thing in e.g. Python.
Database connectivity and probably a few others, does that harm the
success of C? That it just happens that the modern scripting languages
have this stuff is nice, but none of them has anything but a reference
implementation.
So what if you don't care about it what stop you from choosing one
The Balkanization of the CL implementation space also has the
consequence that one must choose between using implementation-specific
features and thus limiting the potential audience for one's code to a
niche within a niche, or writing to the least common denominator, which
generally means writing an awful lot of #+ reader macros.
implementation and "use" it?
Regards
Friedrich
--
Please remove just-for-news- to reply via e-mail.
.
- References:
- How Common Lisp sucks
- From: Ron Garret
- How Common Lisp sucks
- Prev by Date: Re: How Common Lisp sucks
- Next by Date: Re: How Common Lisp sucks
- Previous by thread: Re: How Common Lisp sucks
- Next by thread: Re: How Common Lisp sucks
- Index(es):
Relevant Pages
|