Re:dang, can we get a collapse threads function?
by brudgers on Saturday October 24, 2015 @02:41PM
(#10444462)
I guess dumb luck keeps me from encountering a normal amount of undesirable behavior, while agreeing that folding comments isn't likely to have been anyone's priority. I do see isolated memeoization, flames, etc. but it's not really a characteristic of "core contributors" unlike is more typical of internet communities.
For what it's worth, if indeed PG didn't consider thread folding interesting, I cannot say that I blame him since it is that way for me. The feeling that scrolling through a page to find some comment feels like a bother means that it actually is a bother and not worthy of the effort. Collapsible threads making it less effort to rebut won't increase the quality of my comments...on average, it will probably reduce them. YMMV.
At the very least, I would suspect that particular bit of negative reinforcement failed at its job. A number of other features (karma primarily, but also the comments page and saved stories and saved comments) seem to encourage long term engagement far more than non-folding threads could discourage it. That downvoted comments alone appear on /newcomments practically makes it a flamebait generator. Tribalism, trolling, vindictive nastiness and even meme posting abound here.
On the other hand, I suspect (with nothing to back it up) that pg simply never considered thread folding, or else didn't consider it interesting. Meanwhile, any new feature will inevitably garner criticism from users if it doesn't work they way they expect, doesn't support their browser, etc. And, anything that causes Hacker News to look and behave superficially more like Reddit will cause more than a few users to rend their garments, put on sackcloth and ashes and wail in agony at the death of Hacker News.
That headache, combined with the 'unique' (and not really open) nature of the codebase, a staff with better things to do most of the time, and a strong cultural aversion to making even small changes in the UI, means otherwise apparently simple changes probably take far more time to roll out than many developers would consider reasonable.