None of these are earth shattering, but I would recommend that anyone who writes Markdown take a look at them.
My favorite app for writing long form pieces in Markdown, [Ulysses III](https://itunes.apple.com/us/app/ulysses-iii/id623795237?mt=12&at=10l5TL),[^fn1] has just been updated with some great new features.[^fn2] I highly recommend giving it a shot.
[^fn1]: Affiliate Link (as is the post link).
[^fn2]: My personal favorites are upgraded Microsoft Word export, global search, and auto-completing tags.
David Sparks has released a new MacSpark Field Guide: [Markdown](http://click.linksynergy.com/fs-bin/stat?id=r*bqlTuiXSo&offerid=146261&type=3&subid=0&tmpid=1826&RD_PARM1=https%253A%252F%252Fitunes.apple.com%252Fus%252Fbook%252Fmarkdown%252Fid622433972%253Fmt%253D11%2526uo%253D4%2526partnerId%253D30)[^f2953]. Based on previous books Mr. Sparks has written, and his knowledge of Markdown, I have really high hopes for this. Actually, I am pretty sure I am going to point to it as the definitive guide on how to use Markdown.
[^f2953]: Affiliate Link
If people want to *improve* Markdown, they should just create a fork or new version. For example, Fletcher Penny’s *MultiMarkdown* is what I use for all of my writing. Why does Atwood even need Gruber’s permission and/or help to do that?
Michael Schechter makes the argument against using things like Markdown that might prevent you from moving your data to another platform. Though he makes a good point, I would counter by saying I simply refuse to use a platform that does not support Markdown.[^note]
[^note]: My counter does not relate to his argument regarding his footnotes plugin. I agree with him on that,