Lisp

The real problem with Lisp is that it was designed without any consideration of the cognitive load experienced by the programmer.  The syntax may be simple, but the semantics are extremely complex and hard to master.  This is completely at odds with needs of the programmer. 

The main cognitive load is in developing a solution to the real world problem.  The programmer is engaged in reflective cognition.  Basic UI principles dictate that, when designing tools to aid in reflective cognition, they must as intellectually shallow as possible.  The less cognition required to operate them, the more is available for completing the required task.

Lisp was unintentionally designed for experiential cognition.  It contains many artifacts, each with a very deep and rich set of semantics.  All cognition must be devoted to its operation.  It is no surprise that it only attracts programmers who are only interested in using it for its own sake.

>>41

(>>42 and all of the other ranting messages here)

In Common Lisp? Sure. Please don't mistake my rantings against CL and everyone else on this board as evidence that CL is entirely useless. To answer your question more specifically,

No I mean what kinds of practical applications? Could I write an HTTP request handler or something like that?

It'd be fairly easy, if you're familiar with basic network programming. Check out http://common-lisp.net/project/usocket/ if you're serious. It's a lot of fun to load up usocket (using something like Quicklisp) in SLIME and just play with the library.

If you were expecting something above socket level, I'm afraid I can't say for sure that there's anything you might be interested in. You could check http://www.cliki.net/networking , however, most of those libraries are probably the usual CL pieces of shit that don't work.