3 ms·
> it breaks the UI paradigm to have to go to a different page to continue reading a subthread, and there would be strange consequences (e.g. if you click 'paren
by sillysaurusx 5y ago
> it breaks the UI paradigm to have to go to a different page to continue reading a subthread, and there would be strange consequences (e.g. if you click 'parent' to go to the parent subthread, then the 'more' links will switch to a different set of comments).
For what it's worth, I ran across this situation, and it felt very natural -- but only after adding the descendant count. I'd get curious about a subtree, click into "9 more", read it, see "2 more" on the last comment, and click again. It felt a bit like Numen in that sense.
The flip side of that is, I'm not sure anyone's going to bother writing a long, thoughtful reply after maxnest* depth. They'd have to really love writing for the sake of writing, since orders of magnitude fewer people will see their more'd reply.
But maybe that's a good thing. I don't have the experience to know. If you feel it's fine to change HN's social dynamics like that, you're probably right.
> If we went with the collapse UI for this, we'd have to lazyload the comments on uncollapse.
If this is all a performance concern, please, let me try to fix it somehow. I can work independently on it, and simulate the same number of page views that HN currently gets. I bet you a dollar that I can find a simple, overlooked solution.
I understand that's probably not an option, but email me at shawnpresser@gmail.com if you see a way.
(The reason I'm being persistent about this is, I hate accepting that Lisp can't scale. There must be a way. If there is, I'll find it; as someone whose replies will end up more'd or collapsed, I'm quite motivated to find you a third option.)
Note that my original bug report to you was correct, but initially you weren't sure what I was talking about. (I realized later that you were probably referring to the "more" links at the bottom of the page vs how many toplevel comments show up per page.) I suspect a lot of my past awkwardness with you was due to such miscommunications. I'm not sure why those happen. But all I can do is try to be clear and precise, and only say something when there is something worth saying.
Maybe someday when things settle down, you'll be able to release your HN browser extension. I'm really looking forward to it, whichever year it comes.
Good luck battling the performance beast.