JavaScript is not a LISP (aka LISt Processor) because of these properties: * Lisp is based on efficient procedures (usually with lexical scoping), not objects

JavaScript is not a LISP (aka LISt Processor) because of these properties: * Lisp is based on efficient procedures (usually with lexical scoping), not objects with properties (-> dictionaries) and complex scoping. * Lisp has a code representation based on lists of symbols (and other atoms) and an evaluator model for that. Identifiers in code are symbols. This is typically used both internally and externally (as textual source code). * Lisp is doing list processing at its core and applies it to itself. * Lisp provides forms of source transformations based on list processing: macros, ... JavaScript might be considered to be some non-symbolic non-list-processing Lisp/Scheme derived language, turned into an object-oriented language.