- First name: Gary - Last name: Murphy - Email address: REMOVED - Home page: http://www.teledyn.com - Phone number(s): 519-422-1150 - Postal code: N0H 2G0 - City: Sauble Beach, Ontario - Country: Canada - Organization(s) you work for or study at (please supply the name and city for each organization): XMLTeam Solutions Inc, New York Oriental Passage, Sauble Beach - Fields of interest (e.g. computer linguistics, numerical analysis, business software, medicine, bioinformatics): communications, distributed computing - Have you written any Lisp-related papers? If so, please supply bibliographical references (and URL's, if possible): None - Have you developed or participated in the development of any Lisp-related programs or libraries? If so, please supply a URL, if possible: Only minor contributions to some eLisp packages - Lisp variants you have used (e.g. Common Lisp, Scheme, Dylan): Scheme, Common Lisp, XLisp, eLisp - Lisp variants you're currently using or intend to use in the near future: eLisp - Lisp implementations you have used (e.g. CMUCL, Lispworks, Allegro Common Lisp): Scheme imbedded in various apps like Festival, eLisp, CL, XLisp - Lisp implementations you're currently using or intend to use in the near future: eLisp, Scheme - Computer platforms on which you're using or deploying Lisp: Linux - Number of years of experience with Lisp: 29 (Egad! Twenty Nine Years!!) - Do you use Lisp: - at work (if so, how much) - for study (if so, how much) - as a hobby (if so, how much) very occasional - Are you using Lisp as much as you would like to? No. If not, why not? * Lack of ubiquitous implementations: My projects need to be deployed and it's not likely I'll find any implementations on the target client machine, let alone efficient implementations * Lack of GPL libraries: I hate Perl, loath PHP, but both have a large corpus of GPL libraries that drastically cut development times; in 90% of my work, rapid delivery is far more priority than proprietary or even highly efficient code. * Debugging and Development environments: If something goes wrong in Java, I can find it quickly, and even Perl has Carp, DataDumper and other diagnostics. There may be these for Lisp implementations, but because of the other concerns, I haven't looked. - Do you see any obstacles to further Lisp growth (if so, what is the biggest obstacle in your opinion)? Biggest is the lack of ubiquitous implementations. If mod_lisp was standard in Apache ... - Would you be interested in a Lisp-related job or contract work? Absolutely, Lisp is one of the most natural languages, even more so with OOP extensions. I'd be a little rusty, however - Is your organization interested in hiring Lisp programmers? No. - Are you currently participating in Lisp-related meetings? No. If so, where and how often? If not, would you be interested in such meetings? Not much time these days. - Do you know any other Lispers who might be willing to fill in this questionnaire (please supply their email-address if you do)? A very good question.