A highly recommended read from defmacro.<p><a href="http://www.defmacro.org/ramblings/lisp.html" rel="nofollow">http://www.defmacro.org/ramblings/lisp.html</a><p>Other articles on the site are very nice as well: <a href="http://www.defmacro.org/" rel="nofollow">http://www.defmacro.org/</a>
> Side note: Wouldn't it be awesome if composer supported composer.sexpr files natively, so that we would no longer have to write JSON? No, not really.<p>Why the quick dismissal? I find s-expressions much easier to work with than JSON.
<i>"Stay tuned for follow-up posts."</i><p>For those interested, there was follow-through on the promise to follow-up:<p><a href="https://igor.io/" rel="nofollow">https://igor.io/</a>
> Side note: Wouldn't it be awesome if composer supported composer.sexpr files natively, so that we would no longer have to write JSON?<p>If you, too, think this would be awesome, check out extensible data notation: <a href="https://github.com/edn-format/edn" rel="nofollow">https://github.com/edn-format/edn</a>.
What's great about this is not only that it's a good quick summary, but it left me wanting more. That means I actually feel like I was getting somewhere with it, instead of it being instantly forgotten.
Near the front of the main article is "(sexpr lexer reader eval forms special-forms macros walker)". Each word in the above parenthesized expression links to another article in the series.
Why are the keywords written with a quote?<p>> (keywords '(useless microframework academic swag))<p>Shouldn't it be a list with strings or something? What if the keywords were complex structures not just strings?
If you love the expressiveness of S-expressions but hate the super noisy parenthesis, check the sugar version, called "sweet-expressions". <a href="http://readable.sourceforge.net/" rel="nofollow">http://readable.sourceforge.net/</a>