Relative to his life span, he is new to LISP, but old to C. While he has had more experience in other operating systems (forced to use Mac OS X for work), he is best informed about Linux. He has resolved not to do his job or any C coding until he has regained his love for programming in general. This is where Common LISP comes in, and it's working.
He is a proud vim user and in the same sense a strong believer in the `many small tools' philosophy (as opposed to the swiss army knife philosophy that most modern computation tends toward). He recognizes the ingenious nature of emacs, but he sees it as very awkward and bloated, for an editor. He believes strongly in the FSFs ideals, but he wonders how Stallman will reconcile his ideas on the fairness of proprietary data in the world free software with the equivalence of program and data (which is true in general, but painfully clear in LISP or any language with functions as first class citizens).
He is a computational physicist. He wishes to use Common LISP to aid in prototyping new ideas and data analysis (and maybe, hope among hope, use it for actual high-performance computational tasks such as Molecular Dynamics and Monte Carlo Simulation). He believes (or hopes) that functional programming is the future of computation, particularly scientific computation. He is having some trouble getting past the quite steep learning curve that experienced lispnicks have long since forgotten about (e.g. how to set up your implementation, asdf, asdf-install/pgp keys, cffi/uffi, iterate/series, gray/bordeaux/bivalent-streams, sockets, debugging/interpreting error messages, etc...)
He competed in this last ICFP and programmed in LISP. Actually, as it happens, his teammate was much more effectual in the contest, so most of the work was written in Haskell.
He is currently working through Project Euler using LISP where his brain fails him.
He is trying to stay relatively independent when it comes to implementation and write portable code. He currently uses CLISP, SBCL, and CMUCL in an attempt to stay neutral. He wants to start using ECL, GCL, and OpenMCL. He is only really interested in using/working with free versions of ANSI CL.
This page is linked from: cl-opengl Graduate Student
CLiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively