Common Lisp is a successor ro Maclisp, which was a successor for the original Lisp implementation. Common Lisp was designed such that the old code can be ported to a modernized version of Lisp. This code moved from Lisp 1.5 to Maclisp to ZetaLisp and to Common Lisp.
Scheme OTOH has its own code bases, its own libraries, its own standards, its own books, its own community.
It is a Lisp, but that has become more or less meaningless for practical work. Being 'a Lisp" means practically very little. It's just a name with an unclear definition and less and less practical value. Thus 'a Lisp' means mostly an unspecified bunch of dialects which are in practical terms mostly unrelated.
I prefer a stronger definition, where Lisp means those dialects and their implementation which actually share code, books, libraries, tools.
Otherwise people get the impression of some compatibility, which in real life isn't given.
It's like a family member, which used to carry your name, but now has left the house and has its own life.
Scheme OTOH has its own code bases, its own libraries, its own standards, its own books, its own community.
It is a Lisp, but that has become more or less meaningless for practical work. Being 'a Lisp" means practically very little. It's just a name with an unclear definition and less and less practical value. Thus 'a Lisp' means mostly an unspecified bunch of dialects which are in practical terms mostly unrelated.
I prefer a stronger definition, where Lisp means those dialects and their implementation which actually share code, books, libraries, tools.
Otherwise people get the impression of some compatibility, which in real life isn't given.
It's like a family member, which used to carry your name, but now has left the house and has its own life.