I wasn't being full serious. Personally I take it for granted that CL can be used well in teams just like any other language. Teams are about leadership anyway, which is a seperate concern from choice of language. However, that CL gives you the power to be "lone wolf" (read effective solo programmer) instead of a lone sheep is a huge benefit. I also think that when people decide to learn a comp language, more often than not they do so in their own free time, without other distractions - ie when they are alone. Because of the at-best not so straight forward and dry state of documentation in common lisp libraries (the spec, while dry, is actually really good), common lisp is a bad starter for that type of learner. I mean just the dry style itself looks like it is either not maintained or poorly written. It is a shame because common lisp has great documentation protocols built into the bloody language. Again, I feel this is because seasoned lispers are so capable in reading the actual source code (with assistance of M-. and M-, from Slime) that they just skimp on the documentation.

Some things that I have in mind that would take alot of effort but WAAY less than making another editor competitive with Emacs+SLIME/SLY:

   * Rewrite the spec in org-mode and use babel for interactive learning
   * Integrate the above with the so called de facto standard libraries
   * Make excellent documentation for SBCL and ECL implementations (take CCL as an example)