https://twitter.com/gruber/status/261650083689426945
https://twitter.com/gruber/status/262287246953164800
It's hard to tell, but Jeff possibly seems to be patronizing John a little in the original 2012 blog post [0] with all the bolded statements about John and the bit about the Yankees. Or he could just as well be trying to have a bit of light-hearted fun with it, I don't think we can judge his intentions in this case.
[0]: http://blog.codinghorror.com/the-future-of-markdown/ (Blog link repeated in this comment for clarity)
http://i.imgur.com/tjo9vMg.png
How the Apple fanboy journalist community rallied and circled the wagons was both expected but viscious. Lots of name calling from that side.
Or, it would be, if this were a formal debate. Which it isn't.
But this is totally unrelated to the immature behavior that he's showing about this whole Markdown drama.
I wasn't calling JG that, I was calling all those around him in the Apple tech press who also piled on with the insults like "jackass".
The point is that one side is name-calling and insulting the other, while the other side is trying to advance a technology for a large number of devs and internet users.
I'm just a commenter on HN with little skin in the game, how I conduct myself matters little in this debate. How the primary parties in this story act is important and revealing.
That's a bit misleading. Jeff has been known to rant about Markdown since at least 2009 [1] and decided to do something about it in 2012 [2].
John was contacted at that time. The idea was the following:
I'd really prefer not to fork the language; I'd much rather collectively help carry the banner of Markdown forward into the future, with the blessing of John Gruber and in collaboration with other popular sites that use Markdown.
That did not happen, so they went ahead on their own. Of course I have no idea what John's private reactions were and if that discussion involved naming issues, but this did not come out of the blue.
[1] http://blog.codinghorror.com/responsible-open-source-code-pa...
[2] http://blog.codinghorror.com/the-future-of-markdown/