I'd always understood and used "TL;DR" as "this might be so long and recondite you'd skip it, but here's what it comes down to."
When I first saw it (long enough ago that I'm not making it up), it was most often applied to the author's own answers in USENET groups. People who contributed to the Linux kernel could hardly say they hadn't read their own code.
I'd always understood and used "TL;DR" as "this might be so long and recondite you'd skip it, but here's what it comes down to."
When I first saw it (long enough ago that I'm not making it up), it was most often applied to the author's own answers in USENET groups. People who contributed to the Linux kernel could hardly say they hadn't read their own code.
I'd always understood and used "TL;DR" as "this might be so long and recondite you'd skip it, but here's what it comes down to."
When I first saw it (long enough ago that I'm not making it up), it was most often applied to the author's own answers in USENET groups. People who contributed to the Linux kernel could hardly say they hadn't read their own code.
Oh, forgot: therefore "too long, _don't_ read."