If you mean the C compiled code, that's what a typical sbcl binary is already. On my system it's around 2.5MB. The compiled CL code image (and its related data) is around 50MB. save-lisp-and-die sticks the image into the runtime binary.
The Mark Zuckerberg profile is promoted heavily on "who to follow"-type interstitials. It also shows up when friends like or share things it posts. Blocking would be a simple way to avoid seeing those things, if it worked.
I hope to improve the documentation and security of Quicklisp in the next few months. It will depend on funding.
The core of Quicklisp is in dist.lisp. Understanding the protocol of the generic functions at the start of that file will help clarify Quicklisp as a whole. Almost everything else Quicklisp does is in support of that protocol.
GNU CLISP does not get any resources, human or otherwise, from the GNU project. If Sam stops working on CLISP, he's not going to start working on GNU Emacs or gdb instead.
This is true in the same sense that the GIMP is the "GNU Image Manipulation Program". It's just a label, and a license choice, without much real meaning behind it. GCL is also called "GNU Common Lisp".
Certain things are still hardwired into the Common Lisp reader. For example, because of how colons are treated in symbols, you can't trivially support something like JSON via reader macros. It still works best if the input bears a pretty good resemblance to lisp.
That's not such a big deal, because there are plenty of tools for conventional input parsing in Common Lisp.
I think anyone who wants to be able to stick with a system as they grow, get supportive help from an active user base, reuse the work of others in the form of useful libraries, and not worry about the viability and future of their development environment should use something like LispWorks, Allegro CL, Clozure CL, or SBCL. LispWorks and Allegro CL are just as easy to install and use on Windows as Corman Lisp.
It might have been at some point in the past, but it doesn't run on modern systems, does not fully implement Common Lisp, and can't run much of the useful software written in the past 10 or so years.
It's still pretty cool, but not as a learning tool in 2015.