TL;DR: This Meme Must Die(synisma.posterous.com)
synisma.posterous.com
TL;DR: This Meme Must Die
http://synisma.posterous.com/tldr-this-meme-must-die
10 comments
It originated as a reply. Someone would make a long post, and whatever dork would reply "too long; didn't read". It became a trend, got shortened, and then people started putting the summary in the OP as pre-emptive defense (and because it's useful). I want to say it started on SomethingAwful, but who knows.
This meme was popular on udaff.com (http://en.wikipedia.org/wiki/Udaff) several years ago:
много букаф , ниасилил (too long, didn't read)
много букаф , ниасилил (too long, didn't read)
Yes. But not an acronym, and no summary present.
TL;DR can't be replaced with just "Summary", because it carries much more meaning than that. It's a preemptive retort to any criticism that the original text is too long. You need to understand the full evolution of the term before dismissing its value: It originated from commenters telling an author the text is too long or needs better formatting. Its use as a summary prefix acknowledges and sidesteps this issue.
Rather than simply saying, "Here's a short summary," TL;DR says, "I know this is long and you probably hate me for it, so here's a short summary to mitigate your unhappiness."
Rather than simply saying, "Here's a short summary," TL;DR says, "I know this is long and you probably hate me for it, so here's a short summary to mitigate your unhappiness."
I think that TL;DR is a great practice for writers, and it doesn't matter how you label it.
TL;DR apparently originated on MetaFilter, which I can totally see happening. The sort of esoteric abbreviation coupled with a semicolon would definitely come from there. However, it started as a response to extremely long & rambling posts. Then, TL;DR became used by writers to capture attention-span-challenged denizens.
That being said, TL;DR works pretty well at popping on the page. Being acceptably allcaps, it easily pops out when you're skimming, even if it's in the middle of a paragraph.
Also, I notice that if I'm skimming something pretty interesting, and notice a point of a TL;DR statement that I missed, I'm strongly prompted to go back and read it again. Not that "Summary" wouldn't do this, but it's almost more insulting.
All of this being said, you there are ways you can avoid the issue altogether. If you just more tersely with short paragraphs and bullet points, you can trick people into actually reading. Or, start out your rambling rant with whatever you were going to put as your TL;DR: people generally read the first sentence.
People also read the last thing. Did you skim this comment?
TL;DR apparently originated on MetaFilter, which I can totally see happening. The sort of esoteric abbreviation coupled with a semicolon would definitely come from there. However, it started as a response to extremely long & rambling posts. Then, TL;DR became used by writers to capture attention-span-challenged denizens.
That being said, TL;DR works pretty well at popping on the page. Being acceptably allcaps, it easily pops out when you're skimming, even if it's in the middle of a paragraph.
Also, I notice that if I'm skimming something pretty interesting, and notice a point of a TL;DR statement that I missed, I'm strongly prompted to go back and read it again. Not that "Summary" wouldn't do this, but it's almost more insulting.
All of this being said, you there are ways you can avoid the issue altogether. If you just more tersely with short paragraphs and bullet points, you can trick people into actually reading. Or, start out your rambling rant with whatever you were going to put as your TL;DR: people generally read the first sentence.
People also read the last thing. Did you skim this comment?
TLDR: use 'Summary' instead of TLDR.
;)
Tbh, I'd rather use tldr b/c it's shorter, even if only by 3 characters. And like most acronyms, once you've looked it up once you never forget. But 'summary' is definitely more semantic.
;)
Tbh, I'd rather use tldr b/c it's shorter, even if only by 3 characters. And like most acronyms, once you've looked it up once you never forget. But 'summary' is definitely more semantic.
I always thought TL;DR was more dismissive than "Summary"
I think tl;dr differs from a summary in that it is written as a response to hostility coming from someone who thinks the post is verbose. When I have seen it used, it has consistently been more terse and to the point than summaries generally are. It may seem awkward and inaccessible to those unfamiliar with it, but I do think it is a specific enough form of a summary to warrant its own term.
TL;DR also breaks my brain's English parser. Bad. In the same way that reading .NET in an otherwise legal English sentence tends to annoy me. Character not expected! Abort! Stack trace!
Good luck single-handedly destroying a meme created by the INTERNET.
You're right but that was my point: I'm asking all of you to join forces with me to help destroy this meme. Won't someone think of the kittens?!?!?
TL;DR
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..."
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..."
agreed. TL;DR by itself actually makes sense. It means something distinct from, "in summary: <blah>".
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
Summary: TL;DR Sucks, Summary is Better
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.
More so,
If hn is worth anything, it somewhat reasonable dialog. This particular response just oozes dismissiveness and a willingness to toss out discussion.
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)
"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)
The Russian version of tl;dr is niasilil: http://en.wikipedia.org/wiki/Cacography
that looks and sounds cool at least: niasilil!
My best guess is the usual guess: Either it isn't really a synonym for "summary", or it used to not be a synonym but its original intent wore away over time until it became a synonym.
In this case, "summary" is a neutral term. You can summarize good writing, you can summarize bad writing, and the word "summary" conveys no critical judgement. Whereas my impression is that "TL;DR" was invented not just to summarize but also to criticize: The term suggests that the original is needlessly verbose, and tends to imply that reading the whole original is a pointless waste of time.
But my other impression is that the distinction between a "TL;DR" and a simple "summary" is eroding. This sort of thing can happen when a meme spreads far enough beyond the subculture that invented it: Folks pick up the gist, but miss the subtle colorations. Now I see writers TL;DRing things that are actually good, as a matter of routine. Which makes me suspect (or, at least, hope) that the meme's fifteen minutes of fame will soon be over and we'll go back to using "summary" again.