The presentation seemed to go well, as far as I can tell. Lots of intelligent questions and some interesting side-tracks to pursue.
I find myself in the bizarre position of trying to convince myself of not writing CL code for work (production use). I have this binary log format we need to extract data out of. I have at hand Perl, Python and C APIs but Python is definitely too slow. C is fast, but it's not nearly as flexible writing the analysis tools we need in C (implement another generic hash-table? do explorative programming? in C? no thank you). As soon as I've got some speed data out of teh Python code, I'll bash up the equivalent in Perl and check (basically, the speed-test program opens the log, then reads and entry and updates a counter; repeat until end-of-log; print counter).
I'm testing on 2 minutes worth of log, this is around 43 MB of data. In C, just reading it and incrementing the counter takes about 14 s, says time(1). The python version takes 8m14s to process 2m worth of log. This is quite bad for things that we'd (ideally) would want to process in real-time.
OK, I need to whack things a bit before I can speed-test the Perl version. Aha! It's faster than Python, marginally. 6m49s for a 2m log. Still not fast enough.
Good thing I was moving ahead implementing something that may actually be useful, then.