If you don't have time to read HN, and need TL:DRs then you should question why you are here in the first place.
--
Vote down if you like, I joined HN to get away from inane commentary and TL:DR nonsense that's so prevalent on other sites.
If you don't have time to read HN, and need TL:DRs then you should question why you are here in the first place.
--
Vote down if you like, I joined HN to get away from inane commentary and TL:DR nonsense that's so prevalent on other sites.
There is no joy in being fooled by a clickbaity title. Also, HN is not a novel book, therefore I do not feel spoiled. I always silently thank people that write tl;dr. They try to save my time.
In this case I did it because the title made me wonder if this was the article I read years ago about implementing an ARM emulator for AVR to boot linux. I clicked through, confirmed it was, and that it was a 2012 article. I figured I'd leave the TL;DR as a shortcut for others to confirm they've already read it, not as a replacement of the article for those that haven't.
Next, we'll have people just copy-pasting the entire article body as a comment ... :(
You read the links? I'm just here for the commenting. If the comments imply the article is good enough I'll read it.
(This effect used to be very strong on the Guardian's commentisfree site, where the top comments often contained valuable correction/context to the tritness of the article)
> Next, we'll have people just copy-pasting the entire article body as a comment
I've seen that done a few times; it's useful if it's paywalled/adwalled/unusuable-crashy-javascript-walled.