News for hackers. Stuff that matters.
Re:Ask HN: Does the design of a programming language include... by nostrademons on Monday June 20, 2016 @03:23PM (#11940612)
It's often beneficial to the language for its author(s) to write the compiler as well. Without doing this, there's a tendency to cram every feature imaginable into the language (see eg. ANSI Common Lisp, Algol 68, PL/1), which tends to make it too difficult for anyone to learn or program with. The need to write a working implementation is a forcing function that keeps the language design simple and ensures that the language designer deal with any unintended interactions between features.
Re:Ask HN: Does the design of a programming language include... by lispm on Tuesday June 21, 2016 @03:18AM (#11944026)
Common Lisp is not the all-feature Lisp. It's basically a slightly simplified and improved version of Maclisp successor projects (NIL, S-1 Lisp, Lisp Machine Lisp / Zetalisp, Spice Lisp). Thus Common Lisp basically of similar complexity of prior Lisps.

Common Lisp does inherit very very little from other Lisps like Interlisp, Standard Lisp, etc.

Common Lisp was designed by implementors. If it is 'hard' to program in it, it probably is more BECAUSE it was developed by implementors:

   Gabriel: NIL (New Implementation of Lisp) -> Lucid Common Lisp
   Steele: NIL 
   Moon: Lisp Machine Lisp -> Symbolics CL
   Weinreb: Lisp Machine Lisp -> Symbolics CL
   Fahlman: Spice Lisp -> CMUCL
Even the later ANSI Common Lisp was designed with implementations of its new features. For example CLOS was designed mostly by people from Xerox PARC. CLOS was at the same time implemented by them in a portable implementation called PCL, where the designed was explored and feedback was assembled from a group of users. The very people who wrote the spec for CLOS and a book about it, they also implemented it.