sampsonj

3 ms·

1.
by sampsonj 9mo ago
Oh, one more thing: I should mention that you’ll probably want to fetch documentation only after a code block has been in view for n milliseconds (like what I do in my extension). Otherwise, you risk throttling if a user scrolls very quickl
2.
by sampsonj 9mo ago
Please post here once you have something working, or what you find if you struggle. I would be interested to see if you could get something working and would love to be wrong, as it would be nice to have something similar that does not use
3.
by sampsonj 9mo ago
I agree that parsing codebases and linking code to documentation is a solved problem. I think @ramon156's suggestion to use tree-sitter or something similar to parse an abstract syntax tree makes sense. To clarify my earlier point, I w
4.
by sampsonj 9mo ago
Good point, thank you
5.
by sampsonj 9mo ago
Can you elaborate more. It's still early and I would love feedback
6.
by sampsonj 9mo ago
lol thank you, I was just going to respond to them. One thing I should mention too is that if it were at all practical to build without using generative AI, someone would have built something similar years ago before LLMs.
7.
by sampsonj 9mo ago
Thank you! I will look into these! Yeah, it could be useful for providing explanations of key terms in papers or something similar.
8.
by sampsonj 9mo ago
The LLM approach is simpler and more flexible since it works with every library and language out of the box. Looking up official documentation would require shipping sophisticated parsers for each language, plus a way to map tokens to their
9.
Show HN: Hover – IDE style hover documentation on any webpage(github.com)
58 points by sampsonj 9mo ago|27 comments