We owe much of Clojure's utility and innovation to a *community* of macro
writers. core.match, core.logic, clojure.test, Tellman's Manifold... You
are in deep trouble if you "brute-force" your way around what Manifold
does, by melding the complexity into your application space. And those
libraries are not the work of the language's custodian. They would not
exist without macros.
Fundamentally, a macro is a code generator. Contrast macros not just with
"brute force", but also with the code generators everybody uses with Java:
@annotation processors, IDE plugins, Perl scripts... Significant
complexity arises from these coping mechanisms. Macros are simpler.
But I would agree that you are not missing much if you happily use Clojure
without writing your own macros. Using-more-macros is not a worthy goal.
Right-tool-for-the-job is a much better goal.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
