alt Hacker News> "Is Bob Geldof's hair blue?" -> Search for Bob Geldof -> Look at images of Bob Geldof
Assuming I get images of Bob Geldof. More likely the first page will be pinterest login-required results.
> there's probably a YouTube video about the topic.
Life's too short to watch talking heads about ... you know, WRITING code ...
> can be found at the documentation of the website
Seriously? Maybe for the top 500 npm packages. Not for the more obscure libraries that may have only some doxygen generated list of functions at best.
> Assuming I get images of Bob Geldof. More likely the first page will be pinterest login-required results.
You do realize Google/Bing/DDG/Kagi all have an Images tab, right? Come on.
> Life's too short to watch talking heads about ... you know, WRITING code ...
If I want a high level overview of what the thing even is, a YouTube video can be useful since there will be explanations and visual examples. You can read documentation as well. For example, if I want a slower overview of something step by step, or a talk at a conference about why to use this thing, YouTube can be helpful. I was just looking at videos about HTMX this weekend, hearing presentations by the authors and some samples. That's not saying if I actually use the thing I won't be reading the documentation, it's more just useful for understand what the thing is.
> Seriously? Maybe for the top 500 npm packages. Not for the more obscure libraries that may have only some doxygen generated list of functions at best.
How do you expect your LLM to do any better? If you're using some obscure package there will probably be documentation in the GitHub README somewhere. If it's horrible documentation you can read the Typescript types or do a code search on GitHub for examples.
This is all to say that I generally don't trust LLM output because I have better methods of finding the information LLMs are trained on. And no hallucinations.