5 ms·
Not so. Most of QPX and RES is Lisp.
by sjbach 16y ago
Not so. Most of QPX and RES is Lisp.
- hga 16y agoAs I understand it, C++ to maintain the QPX in-memory database and SBCL to do the routing magic (which is even more non-trivial than you might think, e.g. a "best" result set is not 20 routes that are all within a dollar and that hit the same airports, etc. etc.). RES uses Clozure CL (formerly OpenMCL, an evolution of Macintosh Common Lisp) for the stateless middleware with Oracle RAC for the backend and Java with the usual libraries for the web front end.
- sjbach 16y agoI'm a current ITAer working on QPX -- by lines of code, QPX is probably actually split pretty evenly between C++ and Lisp. But accounting for verbosity of C++, the logic is heavily on the Lisp side. I think anyone on my team would consider himself to be a Lisp developer before anything else.
- KirinDave 16y agoIt's so good to hear this. I'm always afraid that Python is going to squeeze out Lisp. It's a total absurdity, but people seem happy to learn Python and that puts a huge pressure on keeping Lisp shops alive.
- dan00 16y ago"It's a total absurdity, but people seem happy to learn Python and that puts a huge pressure on keeping Lisp shops alive." I think that it's less about learning, because Python is way more similar to languages like Java or C++. Using Python, they have to learn less. Than they discover some cool new features in Python and are bought. Then they don't see any need to bother further with lisp.
- hga 16y agoWikipedia on Blub: http://en.wikipedia.org/wiki/Paul_Graham_%28computer_programmer%29#Blub http://en.wikipedia.org/wiki/Paul_Graham_%28computer_program... The interesting question here is what's getting people to try Python but not a Lisp. Perhaps Clojure will help answer that question.