3 ms·
Your objections seem reasonable, but one of them bothers me more than the others. The error using the special form could be a typo (I'd have had to look up whet
by gruseom 19y ago
Your objections seem reasonable, but one of them bothers me more than the others. The error using the special form could be a typo (I'd have had to look up whether to write (function mapcar) or (function 'mapcar).) The oxymoronic use of "duality" is kind of odd, but given that the author probably hasn't had an editor (or even many proofreaders), I'll cut him some slack.
What really worries me is the dropping of and carping against well-established conventions of the CL world. There's a long tradition of solitary, intelligent but self-thwarting types who take up Lisp and "improve" on it and proclaim how everyone else is wrong. Lisp attracts these kinds of quacks, so this last example is a bad sign. It's not that existing Lisps can't be improved on; the capacity for such improvement is what makes Lisp so great. But the threshold for doing so is high, and I don't think the author meets it here. He's picked a decades-old CL convention that exists for good reason, made a rather weak case against it and summarily excised it... from a CL book whose only audience will be CL enthusiasts? That doesn't seem like very good judgment. Oh well, perhaps the book will still be worthwhile.
This relates to something else that's been on my mind lately. Almost every time I've thought of a "better" way to do something in CL than the standard or conventional way, I've later discovered that it created more problems than it solved and dropped it. Eventually it dawned on me that the designers of CL weren't stupid. More than that, they were cognizant of a broad range of issues when making the decisions they did. It's true that some highly informed people believe that CL is kludgey because of the compatibility constraints that it was designed under, but I think the fact that CL was a generalization over various Lisps and millions of lines of existing code (in many different domains) is also one source of its amazing strength for building production systems. In some fundamental way, the tradeoffs that were made in creating CL seem optimized for what programmers actually do when building complex applications. It's not the most concise or modern language at the code snippet level, but at a systems level CL is so beyond anything else I've seen that I've learned to give its designers the benefit of the doubt. When something seems wrong, it's probably (though not necessarily) because I'm unfamiliar with some of the issues involved.