News for hackers. Stuff that matters.
Re:The Future of Markdown by cdmoyer on Thursday October 25, 2012 @09:20PM (#4700414)
This would be a lot stronger argument without the ad hominem bits. He's obviously not so terrible if he created this thing that has people so up in arms.

I think there's something to your post, but the tone makes me want to dismiss it. I know, stupid emotions.

This internet lynch mob mentality... I wonder how much this discourages people from releasing things. So, Gruber releases markdown.pl. People like it. People love it. People use it, people reuse it, people rewrite it. Next think you know, he's being insulted on the internet because he released something he wrote to serve his needs and not passing on some sort of figurative mantle or blessing.

Re:The Future of Markdown by w1ntermute on Thursday October 25, 2012 @09:43PM (#4700465)
> He's obviously not so terrible if he created this thing that has people so up in arms.

Oh please, double standards like this disgust me. Microsoft had shit slung at it for years on end by the tech community because IE was terrible and held back innovation on the web, but no one claimed that IE is "not so terrible" just because everyone cared about it.

The difference with Gruber is that he's a darling of the tech community because he's Apple-anointed nobility. But as a programmer, in my eyes (and in the eyes of any other objective observers) he's absolute shit.

Re:The Future of Markdown by erikpukinskis on Thursday October 25, 2012 @11:20PM (#4700700)
The reason Microsoft is dead to many developers (myself included) is that they used their massive corporate power to shut down good startups making cool stuff.

I didn't care that IE was terrible (until v3 or whenever), I cared that Microsoft went to all the major PC manufacturers and told them that their licensing deals were toast if they preloaded Netscape.

I didn't care that Word was a crappy word processor, I cared that they used their market position on office documents to make minor incompatibilities that prevented WordPerfect from interoperating.

I didn't care that Windows file sharing wasn't half as good as NFS, I care that they continually fucked with the SMB protocol so that no one could sell UNIX machines that could share with Windows networks.

It has been an absolute pleasure watching that Microsoft's power over device makers disappear. The world is better off for it, and Microsoft will always be an asshole in my book.

Re:The Future of Markdown by angersock on Friday October 26, 2012 @12:30AM (#4700879)
Well thank god we don't have any platform owners today making changes that screw over developers.
Re:The Future of Markdown by Tloewald on Friday October 26, 2012 @07:04AM (#4701664)
There's a differenc between trying to maintain app store policies that strike a balance between security, end user interests, developer interests, profitability, etc. and intentionally putting bugs in your OS to break third party products, stealing third party products and building them into your OS, or bundling free products with your platform or office suite to drive third parties out of a market.
Re:The Future of Markdown by angersock on Friday October 26, 2012 @08:50AM (#4701916)
Agreed that the difference exists--that says nothing though about who's practicing what these days.
Re:The Future of Markdown by squidsoup on Thursday October 25, 2012 @09:48PM (#4700473)
No, the difference is that Gruber is a person whereas Microsoft is a corporation. Corporations aren't subject to the same social mores - it isn't hurtful to say something nasty about a corporation.

Abandoning basic etiquette that you should have learned in primary school and calling someone "absolute shit" is not cool.

Re:The Future of Markdown by skeletonjelly on Thursday October 25, 2012 @09:55PM (#4700486)
While I agree that calling somebody that is not cool, I think you'll find that product owners at corporations do take it to heart when harsh criticisms are called out. They identify with their output.
Re:The Future of Markdown by blasdel on Thursday October 25, 2012 @09:48PM (#4700472)
The thing is this isn't something new, I and a number of other people have been enraged by this for eight years now.

Over those years it's grown in usage exponentially, and so has his fame as a sportswriter for team Apple. Throughout that period he's continued to brush off all kinds of attempts to clean up bugs, define ambiguous behavior, or fix the security vulnerabilities. It hasn't mattered what approach people have taken, he just does not give a shit. Here's an example from last week: http://six.pairlist.net/pipermail/markdown-discuss/2012-Octo...

He's spent so long burning off any goodwill I would have for him on the matter, being cordial just isn't a priority anymore. NERD RAGE.

Re:The Future of Markdown by tptacek on Thursday October 25, 2012 @10:02PM (#4700495)
You've been enraged by the handling of a text-to-HTML converting Perl script written by a tech writer?

You're right: he just does not give a shit. I can see why. What possible upside could there be to engaging with someone who handles themselves like you are here?

Re:The Future of Markdown by stickfigure on Friday October 26, 2012 @12:58AM (#4700924)
You've never been enraged by poorly written tools or technologies? There have been times I wished I could reach through my monitor and throttle some well-meaning idiot for wasting hours or days of my time.

Imagine that you're a mechanic working on a motor that uses the ProprietaryNew fastener (hex heads? so 20th century!). Unfortunately, the only ProprietaryNew wrenches are made out of cheap metal, and the sockets strip with regularity. You can't imagine saying a few nasty words about the parentage of everyone in ProprietaryNewCo?

Re:The Future of Markdown by jopt on Friday October 26, 2012 @03:06AM (#4701187)
Gruber has a long-standing money-back policy
Re:The Future of Markdown by icebraining on Monday October 29, 2012 @08:02AM (#4711865)
What about a time-back policy?
Re:The Future of Markdown by jarek on Friday October 26, 2012 @01:52AM (#4701019)
You have not yet attained the Zen of HN :(
Re:The Future of Markdown by Tyrannosaurs on Friday October 26, 2012 @10:02AM (#4702168)
Actually I think he does give a shit, he just feels that things could be a lot worse than they are and tinkering isn't necessarily going to improve things. Given how widely used it is there is some merit to this argument.

From a comment on Twitter yesterday in response to someone, it doesn't seem that Gruber is particularly interested in engaging with this (though I may be wrong). If that is the case I suspect we'll see a forking of the project and we'll get to see whether a committee will do better.

It may well do - Jeff has a good track record at getting things done and is well respected and well liked - but personally I wouldn't put my mortgage on it because as well intentioned as these things are we all know how design by committee usually turns out.

Re:The Future of Markdown by bigiain on Thursday October 25, 2012 @10:45PM (#4700604)
"Enraged" huh? For "_eight years_"?

Care to show us your alternative? It'll be on Github or GoogleCode, or maybe your personal blog, somewhere we can download it, try it out, and criticize it too, right?

Surely 8 years of rage is enough encouragement to write your own replacement for ~1000 odd lines of Perl?

Or by "enraged", did you mean "annoyed enough to write critical posts on random internet sites, but not motivated enough to spend an evening or two solving the problem myself"?

"NERD RAGE" indeed…

Re:The Future of Markdown by blasdel on Thursday October 25, 2012 @11:03PM (#4700652)
There are many great reimplimentations, another would only compound the interoperability issue.

The real problem cannot be solved without some forward action on his part. He has refused over and over again.

Re:The Future of Markdown by bigiain on Thursday October 25, 2012 @11:18PM (#4700697)
"The real problem cannot be solved without some forward action on his part."

Sure it can - you write something better, then get everybody who's already using Gruber's version or one of it's presumably also-flawed reimplementations to switch to yours. Or, is "8 years of enragement" really just keyboard-warrior-hyperbole on your part and an excuse to criticize someone who's achieved widespread adoption of some code you claim is 2nd rate, but which haven't bothered to improve or replace?

Besides, it sounds to me like David Greenspan has come up with a fine solution.

Re:The Future of Markdown by jopt on Friday October 26, 2012 @03:08AM (#4701189)
This is bot a privilege issue. Nobody appointed Gruber. Just do a better job and you'll be fine without his permission.
Re:The Future of Markdown by SCdF on Thursday October 25, 2012 @09:43PM (#4700464)
> He's obviously not so terrible if he created this thing that has people so up in arms.

Being great at designing a format and writing code are two different things: one can be great at once while being terrible at the other.

Re:The Future of Markdown by blasdel on Thursday October 25, 2012 @09:52PM (#4700480)
The perceived simplicity of the format (driven by the naivete of the implementation) played a significant role in making it popular, but lays a minefield of bugs and ambiguities for implementors especially if they want any combination of sanity and interoperability.
Re:The Future of Markdown by gordonguthrie on Friday October 26, 2012 @12:07PM (#4702820)
Wisest thing in this thread.

It is a great format.

The original parser (and specification) has serious problems.