Thanks @gemath for your thoughts. It is true that the priority is to carry Nim to well deserved 1.0 release at the moment but I think at some point not in the very far future, nimble should be improved and rehandled. I guess it is already in the roadmap.
There are guidelines in nimble github page. Maybe, somehow, it may check some conditions before letting the package into the package list. For example, it may enforce to have at least one version tag in the repo and versions strictly increasing Maybe, the guidelines can be extended so that every package has some standards. (Proper README.md, proper nimble file etc.) Regarding a package manager with binaries, what I mean by binaries is not the binaries generated by nim, but binaries of a library that is wrapped with nim. The nim code can still be in source code form. But if it can pack the binaries of that library as well, then the nim developer will deal with only the nim code, he/she won't need a different build system or knowledge to build the original library. I know it requires more maintanence and it does not have high priority. But I guess, it may increase ease of use, adoption of the language. Nim has great potential and I really wish it becomes a mainstream programming language (if not the first). As in the [community survey](https://nim-lang.org/blog/2018/10/27/community-survey-results-2018.html) , people would like to see Nim as a product, (Maturity, Reliability, Documentation etc) with all the elements. Nimble is also an important part of the ecosystem and I believe it will improve together with Nim and what is done to it will contribute to Nim as well.
