2 ms·
I think CL was born of a culture of Lisp infighting. For example, the CL / Scheme rift makes little sense to me and probably has deep historical / political roo
by hga 14y ago
I think CL was born of a culture of Lisp infighting. For example, the CL / Scheme rift makes little sense to me and probably has deep historical / political roots that don't interest me that much.
Well, the former is true; CL was a very successful attempt to unify the existing mainline LISPs and while adding the lexical scoping of Scheme. That process was inherently political, and I'm told the phrase "sufficiently clever [or smart] compiler" was used rather too often, e.g. to get some inherently expensive off of Lisp Machines stuff into it).
Scheme has very different objectives. It started with a clean slate, threw away a lot of historical baggage and it's a Lisp-1 instead of a Lisp-2 (single value for an atom, does not potentially have both a value and function), and since its initial development has stressed simplicity and correctness (i.e. figuring one correct way of doing something), which have never been mainline LISP goals. E.g. look at the mission statement from the beginning of the standard's documents:
Programming languages should be designed not by piling feature on top of feature, but by removing the weaknesses and restrictions that make additional features appear necessary. Scheme demonstrates that a very small number of rules for forming expressions, with no restrictions on how they are composed, suffice to form a practical and efficient programming language that is flexible enough to support most of the major programming paradigms in use today.
The premise is debatable (and Scheme has not particularly broken out of the niches of language work and education), but it's very different than mainline's LISP's.
So while their might be a "rift", there never was any chance for anything else. Schemers are not going to add a lot of legacy LISP to their language (let along become a Lisp-2) so that they can run legacy mainline LISP code, Common Lispers, even if they don't have an existing code base, have needs that are not as yet satisfied by Scheme due to its very slow standardization process and the false start at addressing them in the deeply flawed and largely rejected R6RS.