Here&#x27;s an example of why arc&#x2F;lisp are great:<p><pre><code>    (mac awhen (expr . body)
      `(let it ,expr (if it (do ,@body))))
</code></pre>
This basically add a new syntax to the language. How often did you do in python:<p><pre><code>    some_value = my_function()
    if some_value:
      call_something_with(some_value)

</code></pre>
With the small macro defined earlier, we can do:<p><pre><code>    (awhen (my_function)
      (call_something_with it))

</code></pre>
Basically, binding (my_function) to the variable named &quot;it&quot;.<p>It&#x27;s amazing to be able to add new syntax&#x2F;features to the language without having to wait for a new version. Imagine if you could add any features you want to javascript or python without having to wait 5 years for the spec to be approved and implemented..<p>It&#x27;s possible because the code is written in the same data structure that you use to manipulate normal values. I.e.:<p><pre><code>    (let x 1
      (prn x))
</code></pre>
Is the code of the program but <i>also</i> simply a list of 4 elements. And since the code itself is a data structure that you can manipulate with normal functions, there&#x27;s something called &quot;Macro&quot; in Lisp (not to confuse with C++ macros), which essentially are functions that receive code and returns code, instead of receiving values and returning values.<p>So: (some_macro (prn 1)). some_macro would receive a list of two elements (prn and 1) and could do some operation to it and returns some new code.. such as (prn 2), which will then get evaluated to print 2. Whereas (some_fn (prn 1)) would evaluate (prn 1) (which returns nil), and pass nil to some_fn.<p>That&#x27;s why it&#x27;s so hard to impress a lisp programmer with any other languages because if a feature doesn&#x27;t exist, they can add it with a macro. I.e. Actors or OO, or whatever really.