title: What's so bad about Template Haskell?
body: <p>It seems that Template Haskell is often viewed by the Haskell community as an unfortunate convenience. It's hard to put into words exactly what I have observed in this regard, but consider these few examples</p>
  
  <ul>
  <li>Template Haskell listed under "The Ugly (but necessary)" in response to the question <a href="https://stackoverflow.com/a/10849782/208257">Which Haskell (GHC) extensions should users use/avoid?</a></li>
  <li>Template Haskell considered a temporary/inferior solution in <a href="http://www.haskell.org/pipermail/libraries/2012-May/017815.html" rel="noreferrer">Unboxed Vectors of newtype'd values</a> thread (libraries mailing list)</li>
  <li>Yesod is often criticized for relying too much on Template Haskell (see <a href="http://www.yesodweb.com/blog/2011/04/yesod-template-haskell" rel="noreferrer">the blog post</a> in response to this sentiment)</li>
  </ul>
  
  <p>I've seen various blog posts where people do pretty neat stuff with Template Haskell, enabling prettier syntax that simply wouldn't be possible in regular Haskell, as well as tremendous boilerplate reduction. So why is it that Template Haskell is looked down upon in this way? What makes it undesirable? Under what circumstances should Template Haskell be avoided, and why?</p>