News for hackers. Stuff that matters.
Re:Better performance in App Engine with new Lisp language C... by mahmud on Tuesday May 11, 2010 @07:12PM (#1339554)
Common Lisp lacks a standard modern way to network I/O

http://common-lisp.net/project/usocket/

Re:Better performance in App Engine with new Lisp language C... by jgg on Tuesday May 11, 2010 @11:14PM (#1340047)
Common Lisp has no standard way of doing Network I/O. usocket is one of several available socket libraries which don't exist in the ANSI spec.
Re:Better performance in App Engine with new Lisp language C... by mahmud on Wednesday May 12, 2010 @10:14AM (#1340975)
It is a de facto standard. Everyone uses it; just like the Metaobject protocol.
Re:Better performance in App Engine with new Lisp language C... by jgg on Wednesday May 12, 2010 @11:24AM (#1341163)
If the usocket library suddenly disappeared, along with all the current Lisp implementations, there would be no guarantee that someone making a new CL implementation had to implement the library in a way similar to usocket, or even implement a socket library at all. It's the same as saying "everyone uses Emacs to edit Common Lisp, so it's the standard Common Lisp editor".
Re:Better performance in App Engine with new Lisp language C... by mahmud on Wednesday May 12, 2010 @09:35PM (#1342932)
What is the standard way for network I/O in C, C++, Python, PHP and Ruby?

I am not in the business of conjuring up hypothetical situations about the demise of Lisp implementations and libraries; that doomsday scenario of having to recreate civilization from specs is simply not in my contingency plan :-)

Never underestimate the power of convention, de facto is the rule, rather than the exception.