@ingo that is too funny. i came here to post something very similar. i wanted to say that the nim ecosystem should seriously consider adopting a voluntary (but advocated and preferably assisted/cooperative.) documentation standard and effort. The docs for many of these libraries are not what someone would expect coming from higher level environments like web development with big frameworks.
The readme's have different info, missing key info, etc. The examples are many times bare bones, missing major use cases, and confusing for people new to lower level stuff like systems languages. I didn't know the examples were there at first. Then, when i found them they confused me. Some of them still do. They should not be used in lieu of a proper readme, and preferably a wiki/knowledgebase with actual instructions. It's poor form to spend all that time writing a library, and then not have the respect for your own project, or the potential user, to put a little effort in the docs. It makes it seem like you don't really care if people use it or not, which creates a lack of confidence in the longevity and professionalism of the project, the ecosystem, and therefore the lang. You want to grow nim? Have a well-defined, base documentation standard ecosystem-wide and aim high.
