@jzakiya I have read a lot in this post, but due to my own lack of time I decided to skip most of it (so apologies if somebody mentioned this already).
Why doesn't Nim have better docs? Some reasons: * Nim doesn't have full-time employees working on it (this is also why telling us "you should get on it" doesn't achieve anything) * Nim isn't v1 yet, so creating docs is difficult (because things change constantly) * Doc writing is boring Nim is a community project. Everybody that works on it, does so out of love for the project. Telling us to "get on it" is unfair and rather ignorant. To help illustrate my point better: you mentioned Nim by Example and Rust by Example. Both are community driven projects. Check out the people that helped create these projects: * [https://github.com/rust-lang/rust-by-example/graphs/contributors](https://github.com/rust-lang/rust-by-example/graphs/contributors) * [https://github.com/flaviut/nim-by-example/graphs/contributors](https://github.com/flaviut/nim-by-example/graphs/contributors) If you want to help improve them then make a PR. Creating documentation PRs is the easiest thing in the world (but also the most boring, which is why people rarely do it). So, what's your excuse? In the time that you've written these posts you could have gone in and fixed the problems instead of talking about them. If you don't know where to find things, then ask, I'll happily guide you.
