When I read documentation and both info and man are available, I decide by content, not by the format. As I don't have to write either manpages (in troff format) or info pages (in texinfo format) I don't have to decide which one is better.

Now if I can just figure out how to get out of the never-to-be-sufficiently-accursed 'info' browser

I can understand if you don't want to learn using the info browser, it is indeed a bit difficult to use. Thus, let me give you some hints.

If you want to learn using the info browser anyway, there's a short tutorial for it that tells only about the most important commands. You invoke this tutorial by pressing h in the info browser. (There're two ways to start an info browser, one is to run the command-line info program, the other is to use the info browser in emacs. These are two separate implementations but their interface is virtually the same.) Btw, you quit from the info browser by pressing q, or, if that types a letter q, hit control-G a few times and then q. If you started emacs, get out of it with control-X control-C.

If you don't want to learn about the info browser, you don't have to. The info browser is really nothing but a fancy (and difficult to use) pager. The info files are really almost plain text, so you can read the info files with any pager, except that you may have to gunzip the info files and concatenate them if they're broken to smaller pieces. This can be done automatically by e.g. info -o ./libc.txt --subnodes libc (this method loses any text in the info file that's not part of any node, and the \x1F chars separating the nodes, but you don't need those anyway).

If you don't like plain text, you can also compile the texinfo sources to pdf, html, or other formats. This is because the info files you see are usually not the source, but are automatically created from texinfo sources by the makeinfo programs. (Makeinfo can output info, plain text, html, xml, or docbook; while dvi, postscript, and pdf are created by processing the texinfo source with the tex program only using a special format file.) However, as normally only the info files are installed, you don't have the texinfo sources, so you have to get the source package of any program to make a pdf or html documentation, and you have to use some special make target. (This is quite similar to perl, which normally installs only man documentation, but you can compile the pods to html or other formats if you choose a special config option.)