3 ms·
I only post a 927 when there are >6 different standards in the field, and there's no way a new one will catch on. As for the effort better spent posts, those ar
by qwertyuiop924 10y ago
I only post a 927 when there are >6 different standards in the field, and there's no way a new one will catch on. As for the effort better spent posts, those are awful. Never post those. Instead post about how great emacs is compared to vim: you're more likely to spawn useful discussion.
- Semiapies 10y agoAnd if you post the xkcd link to a discussion about a piece of software and not a new standard for which many already exist, (and I see that post,) I will proudly downvote you no matter how many examples exist. Just be glad I don't have the magic ability to force anyone to use QED to program their next project in Fortran on a CTSS box.
- qwertyuiop924 10y agoYeah, just don't post 927 on software: that's dumb. Note I said when a new one won't catch on, or is unlikely to do so, particularly of it doesn't have any significant benefits over what's already there.
- deleted 10y ago[deleted]
- 50CNT 10y agoI think that it's interesting that there is an etiquette developing on when which XKCD is appropriate.
- qwertyuiop924 10y agoXKCD is always appropriate when it's relevant, pretty much. There's only etiquette for 927.
- Semiapies 10y agoWell, here. It's still popular on Reddit to be the first to post an "obligatory" link to a vaguely relevant xkcd. Here, that usually gets downvoted fast.
- qwertyuiop924 10y agoI do it sometimes, but only if the XKCD is actually highly relevant. As a result, I've actually never gotten downed for it.
- kuschku 10y ago> As for the effort better spent posts, those are awful. Never post those. Except, the issue is when there’s already dozens of standards in the field, and someone decides to make yet another one, and publish factually wrong articles about existing standards to get an advantage.