3 ms·
I'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++,
by sjbach 16y ago
I'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.