Hello,

awesome program, yet flawed docs.   For example on 
main wget doc.html   user-agent is discussed.  But not 
one link in that section to "what is it?"  "why use it" and 
"examples".  Thus, you would talk about tables of 
possible strings ,  how to use it to avoid ads with off brand 
ids, get into sites that bar non IE users, and how to 
promote your favorite browser. etc.    I think many 
developers, when not restrained by need to sell the 
product, are fearful of being preceived as stupid if they 
make things too easy or clear.  What is so hard as "what" 
"why? when to use? Recommendations?" "examples?"?

Additionally, in overview, an entire scope of the products 
use and limitations really aren't discussed in much detail.

Naturally, the biggest problem with command lines, is 
that most people type with many errors and aren't really 
good at proofing.  Imagine how long letter writing would 
be if error free---every comma--were needed. This could 
be over come with a verbose error report [fix suggestion], 
or better forgivingness, or even that gui written in basic 
that writes them for you.



Reply via email to