cleanup of library docs

web/nimrod.ini

@@ -28,7 +28,9 @@ srcdoc: "pure/complex;pure/times;pure/osproc;pure/pegs;pure/dynlib"
 srcdoc: "pure/parseopt;pure/hashes;pure/strtabs;pure/lexbase"
 srcdoc: "pure/parsecfg;pure/parsexml;pure/parsecsv;pure/parsesql"
 srcdoc: "pure/streams;pure/terminal;pure/cgi;impure/web;pure/unicode"
-srcdoc: "impure/zipfiles;pure/xmlgen;pure/macros"
+srcdoc: "impure/zipfiles;pure/xmlgen;pure/macros;pure/parseutils;pure/browsers"
+srcdoc: "impure/db_postgres;impure/db_mysql;pure/httpserver;pure/httpclient"
+srcdoc: "pure/ropes"
 
 webdoc: "wrappers/libcurl;pure/md5;wrappers/mysql"
 webdoc: "wrappers/sqlite3;wrappers/python;wrappers/tcl"

web/question.txt

@@ -48,6 +48,15 @@ and a substantial body of other code. Until version 1.0.0 is released, slight
 incompabilities with older versions of the compiler may be introduced.
 
 
+How fast is Nimrod?
+-------------------
+Benchmarks have not been ported yet and support for threads is missing. But in
+the worst case, you can get exactly the same performance as C if you decide to
+write as low-level Nimrod code as C requires you to do. That said the only
+overhead Nimrod has over C is the GC which has been tuned for years (and is 
+significantly faster than the Boehm GC).
+
+
 Compilation
 ===========