3 ms·
I have read this piece before but I mostly disagree. "Putting aside Usenet as a relic and artifact of the past, [...]" I think this is a crucial sentence for
by bhaak 10y ago
I have read this piece before but I mostly disagree.
"Putting aside Usenet as a relic and artifact of the past, [...]"
I think this is a crucial sentence for the whole post. He brushes aside the probably best example for a threading model. He never asks the questions "why did it work on Usenet?", "why didn't/doesn't it work on the browser?", and "could we make it work in the browser?".
Most of his arguments concern wrong UI designs for a threaded model. For example "you are talking to everyone". The argument that the reply button leads people to reply to the wrong message is completely refuted by reddit. It's just that the location of the reply button has to be carefully chosen and on reddit they have done it right. There's one reply button for the thread and one on every message.
I usually can accept opinionated design decisions but in the case of discourse, they implemented a half-assed solution. You can expand replies in discussions but then you can't drill down and expand the replies to those replies.