News for hackers. Stuff that matters.
Re:TL;DR: This Meme Must Die by jonpaul on Friday June 25, 2010 @11:55PM (#1463058)
TL;DR
Re:TL;DR: This Meme Must Die by kevinherron on Saturday June 26, 2010 @12:03AM (#1463072)
You see, this is the intended use; in this context it makes sense.

In the context in which you are providing a summary you are saying "I read this, and for those of you who think "TL;DR" here is a summary..."

Re:TL;DR: This Meme Must Die by mkramlich on Saturday June 26, 2010 @01:33AM (#1463182)
agreed. TL;DR by itself actually makes sense. It means something distinct from, "in summary: <blah>".
Re:TL;DR: This Meme Must Die by mkramlich on Saturday June 26, 2010 @01:30AM (#1463178)
That's funny! :) I guess I should have made the article shorter so you could have gotten to the very end of it, which was:

Summary: TL;DR Sucks, Summary is Better

Re:TL;DR: This Meme Must Die by joe_the_user on Saturday June 26, 2010 @12:03AM (#1463071)
I agree with the parent ...

More so,

If hn is worth anything, it somewhat reasonable dialog. This particular response just oozes dismissiveness and a willingness to toss out discussion.

Re:TL;DR: This Meme Must Die by mkramlich on Saturday June 26, 2010 @01:27AM (#1463172)
Yep, "too long / didn't read" has a negative vibe, it's both dismissive and a little insulting to the author of the target piece. Plus, it makes the person saying it look a little lazy or lacking the ability to focus and read through anything longer than a sound bite.

"Summary: <whatever>" is nice because it is impersonal and provides a useful service to other readers. Here is a brief summary of what the piece is about. Useful and not impolite.

(--btw, I'm the author of the "This Meme Must Die" article being discussed, Synisma)