But my point was that the gnu ideology was pushing contributors to use info pages (which many of us (myself included) tend to not use.
So perhaps the ideology should be reexamined from time to time. In this case, it should be: how do we make sure documentation is of highest quality and availability to our users (I'm more than happy to be challenged on that).
In that case, it might be worth considering making man pages a first class citizen again, along with html, as those are the natural destinations a user turns to when looking for help.
Not that there’s anything wrong with using Google or ChatGPT to find what you are looking for, but info is a fast way to get authoritative information, and the documentation is also mirrored on the web so it can be easily indexed by search engines and LLMs.
I think I would prefer we just ship folders of markdown or HTML that open with your editor/viewer of choice though.
And even then, often the best results you get from google come from the man or info page anyway.
My first search when googling documentation for a tool is often "man <toolname<"
For home projects, I have microsoft's docs on C++ and C# downloaded locally, but for work I need to be connected to the internet to do my job
Thanks for telling me that microsoft's docs on C++ and C# can be cached locally. I tried to create local copies of some docs on web programming, but found out that it cannot be done with a reasonable amount of effort by people who are not already experts in web programming.