This sort of criticism is bar-none the most typical negative criticism any time someone describes a benefit of a language, especially an unfamiliar one like Lis

This sort of criticism is bar-none the most typical negative criticism any time someone describes a benefit of a language, especially an unfamiliar one like Lisp. You give code, “this is way too detailed, what’s the essence?” or “how is a for-loop macro special at all? we have for-loops already” You give small simple snippets, “not real world!” You don’t give code, “not enough detail, just feel-good marketing!” You give pseudocode, “well I want to see the real thing!” The concepts presented in the article are hardly about code anyway! They’re about a development workflow and a language environment supporting it. How should the author demonstrate interactive development through a paragraph of text, besides just describing it? You really need a live demo to see how everything moves around, not a code snippet. My suggestion to you as a critic is to actually ask, in good faith, for something substantive you want to see. For instance, “I wish $AUTHOR showed us what they mean about removing a class slot.” Then the author, or others, would be happy to respond to you.