It&#x27;s simpler than it seems, and how strange people make it out to be held me off for a long time.<p>There are cons cells. A cons cell is basically an untyped tuple. The syntax for a cons cell containing a number look like this: (1 nil) (where nil is the zero byte (I think, please correct me if I&#x27;m wrong)).<p>You can nest them, like this: (1 (2 (3 nil))).<p>Because nobody can be bothered to type those parens, the part of the compiler&#x2F;interpreter called the Reader compiles syntax like this<p>(1 2 3)<p>to this<p>(1 (2 (3 nil))).<p>After being parsed by &quot;the reader&quot; (you could also call it &quot;parser&quot;), those nested tuples&#x2F;cons cells are sent to eval function. The eval function takes the first element of the list (aka `car` in lisp-speak. My mnemonic is that a is to the left of the keyboard, therefore means first element). That first element is being regarded as the function, and the second element in the cons cell is the argument to the function.<p>The function to get the second item in the cons cell is `cdr`. I remember that by having `d` being to the right on my keyboard. (car 1 2) =&gt; 1. (cdr 1 2) =&gt; 2. (cdr 1 (2 (3 nil))) =&gt; (2 (3 nil)). That is how things are nested.<p>I digress. The eval function evaluates every symbol (aka atom) in these nested cons cells, and looks up the corresponding meaning of them in a big table of defined symbols. So the + symbol might match an addition function, the string-join symbol might match to a function for joining strings.<p>What is returned from eval you could say is the true AST, which still looks pretty darn similar to the lisp syntax. The function is then sent to the apply function, which applies the argument to the function. Remember that the argument can be a nested set of cons cell, so it can nest infinitely.<p>That&#x27;s it! I&#x27;m no lisp expert, so if someone is, please correct me. But that&#x27;s the gist of it. Syntax is read by the read function, the symbols are interpreted (lookup in a big key-value object) by the eval function, these function gets apply-ed with their argument. Very few primitives are needed by build a system from that. Here is a list of the primitives needed - these can be implemented in binary, C, assembly, Java, Javascript or whatever: <a href="http:&#x2F;&#x2F;stackoverflow.com&#x2F;a&#x2F;3482883" rel="nofollow">http:&#x2F;&#x2F;stackoverflow.com&#x2F;a&#x2F;3482883</a>.<p>BONUS SYNTAX:<p>If you want a eval to skip over a cons cell (and of course it&#x27;s children), you can prepend it with a `&#x27;` symbol. So (cdr 1 &#x27;(this is never going to be evaled, but is just a list)) =&gt; (this is never going to be evaled, but is just a list)<p>This is called a &#x27;quote&#x27;. Any Javascript array is basically working like a quoted list. If the first item in a javascript array was a function, and you applied the cdr of that array as argument to that funciton, it would be like using lisp with an not-quoted list.<p>BONUS VIDEO:<p>This is just lovely. I&#x27;m not American, and do not have a CS degree, so I feel like attending a place like this is a far dream. But happy to be able to enjoy it over the interwebs.  Incredibly thankful to the giants of computing on whose shoulders we can stand <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=2Op3QLzMgSY&amp;list=PLF4E3E1B72A58B492" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=2Op3QLzMgSY&amp;list=PLF4E3E1B72...</a>