Re:Show HN: More HN
by melvinroest on Tuesday September 08, 2020 @04:52AM
(#24406492)
Fair enough, I was hoping this HN discussion was enough. I wanted my code to be a discussion piece, or a starting point to improve. I don't think it's that usable for many people.
Re:Show HN: More HN
by melvinroest on Monday September 07, 2020 @08:33PM
(#24404123)
Hey, I quickly made this Chrome plugin in an hour or so to get all HN comments on one page. I hope there happen to be better versions of this out there, which is why I opened this thread to start a discussion about it.
And if there aren't any alternatives, then let's improve this together!
Re:Show HN: More HN
by pvg on Monday September 07, 2020 @11:31PM
(#24404969)
The best alternative is probably just not-doing that - the reason for the page splits is the performance of the HN back-end and hitting the site for all the follow-on pages might make the problem worse, not better.
It was amazing to see similar code and to see how they approached things. Of course, if only really worked with snippets, but as a learner it was truly amazing.
Re:Show HN: More HN
by beliu on Thursday September 10, 2020 @02:34PM
(#24435201)
If you're looking for a GCS replacement, Sourcegraph is a thing! We've taken a lot of inspiration from Google Code Search (both the public version and the internal version which was even better): https://sourcegraph.com
Re:Show HN: More HN
by gremlinsinc on Tuesday September 08, 2020 @07:10AM
(#24407248)
why not autoload it on scroll... like after you get past 75% or something? Many sites have never-ending scrollers, FB as an example and you'd think as big as YC is they could afford someone who can figure out endless scrolling.
Re:Show HN: More HN
by wolfgang42 on Tuesday September 08, 2020 @12:10PM
(#24409785)
Endless scrolling was specifically rejected [1], and given how vociferous the HN community can be about such things I don’t blame them.
Also, comments can shift from page to page as their ranking changes, so a naïve implementation would end up with duplicates (for comments that fell down past the page boundary before the next page loaded) and missing items (for comments that rose up), and a more sophisticated implementation probably wouldn’t be worth the effort for something they want to get rid of.
Easy improvement: A readme.md It'd be much easier to grasp what it is trying to achieve if it actually were described.
And if there aren't any alternatives, then let's improve this together!
https://en.m.wikipedia.org/wiki/Google_Code_Search
It was amazing to see similar code and to see how they approached things. Of course, if only really worked with snippets, but as a learner it was truly amazing.
I really wonder if they kept it for internal use.
Also, comments can shift from page to page as their ranking changes, so a naïve implementation would end up with duplicates (for comments that fell down past the page boundary before the next page loaded) and missing items (for comments that rose up), and a more sophisticated implementation probably wouldn’t be worth the effort for something they want to get rid of.
[1]: https://news.ycombinator.com/item?id=23195291
I mostly want it when I simply want to CTRL + F the whole thread on certain keywords.
I'll create a toggle to minimize server load.