I wonder how the Lisp I'm using got its Cocoa user interface. Oh, it has an Objective C bridge, so that it can create natively looking Mac applications...
CCL is also not dead.
Not really true these days, with the prolifiration of high-level-languages most libraries present a C interface which is no harder to bind to lisp than to other languages.
Since everyone else is jumping on this point, I might as well also point out that there are things like Chicken Scheme that actually transpile to C and are therefore compatible with it (and anything else that's compatible with C).
> and C is faster than Lisp and people are totally okay with writing code in it.
While C is indeed faster than Lisp (sometimes, at least; IIRC, some Common Lisp implementations like SBCL come within the same ballpark depending on the code being worked with), people are decreasingly comfortable with it as alternatives emerge and the cost of running a high-level language decreases (originally due to Moore's law, but nowadays also due to better-optimizing compilers and interpreters). I expect that we'll eventually hit a point where - much like how it's very difficult (if not borderline-impossible) to produce hand-written assembly that's faster than what a compiler will generate - it'll also be very difficult to write any sort of low-level code in a way that's faster than what a HLL compiler will spit out.
tl;dr: They had special hardware that aided in dynamic language processing, like 40-bit words and hardware dynamic dispatch.
And it would not help you at all today because the most prohibitive part of the system is really the size of the CPU silicon wafer and its efficiency, and C is faster than Lisp and people are totally okay with writing code in it.
EDIT: RE: getting into Lisp in a big way: https://web.archive.org/web/20080709051856/http://www.lambda... tells you all you need to know. Specifically:
"And the problem with Lisp? The answer is tailor made for the minds who program it. It is the koan of Lisp.
"The answer is that there is no problem with Lisp, because Lisp is, like life, what you make of it."
Your Lisp code (unless it's an emacs tool) will never work with anything or anyone else. You're invited to write everything from scratch, and doing so is easy; it's just difficult for anything you do to be used by or with anyone else's code.
Lisp is so beautiful, and yet so dangerous.