A recent article examines how GCC can indirectly call nested functions without requiring an executable stack, addressing a long-standing security vulnerability. The accompanying reader discussion reflects on the historical use of self-modifying code and executable memory in early systems like TeX and Lisp machines, contrasting past performance optimizations with modern security restrictions.