The whole point is that plenty of people are NOT going to help improve the docs, and a lot of those people are people that I'd think people would welcome as Nim users.
If accelerating adoption isn't a goal, then there's nothing to do. But assuming it is a goal, the question is, what are the most important barriers, and what, if anything, can be done about them? I was a Python user from Python 1.0.x days (1994), and wrote the first prominent thing in Python (Mailman, for which I apologize). Python became very prominent quite quickly, because the only languages in the "scripting" niche that had any traction at the time were Perl and Tcl, and Tcl was even more hot garbage than Perl. According to the Tiobe long-term history, Python was already a "top 25" language before I was using it, and cracked the top 10 somewhere around 2004. Yes, ML helped vault it to #1, but it already had a LONG reputation of being, on average, the language people want to code in if they are given a choice (for instance, by the online programming school-type sites). I just looked at those rankings and was sad, and somewhat surprised, that Nim isn't even listed in the top 100. So Nim is NOWHERE near Python in terms of its growth curve. But it deserves to be. Languages succeed and/or fail for plenty of reasons, often not on the technical merits. Having a big tech firm basically spend a lot of money to push the language has a long history of success. It has worked worked for C, C++, Java, JavaScript, Go, Rust, ... But Nim currently doesn't have that luxury. Maybe that's achievable, and if it is, then hopefully it will have a big impact. But, Python is an example where it's possible to dominate without corporate sponsorship. You do start off with a handicap, but in order to really grow, you need to figure out what your barriers to adoption are, and work on those. If you don't think documentation is a major one, then you should still be considering what those barriers are, and how the community can work together to remove them. But it's certainly the case that some "good" developers don't end up in the Nim community in no small part because the docs aren't quite doing the job in giving them a smooth onboarding. Maybe that's not the most important thing to fix, but dismissing it because YOU have no problem with the docs is not going to help Nim become more successful. To be clear, I personally have no problem with the docs relative to my own work. I just think we shouldn't stick our heads in the sand and pretend that it isn't keeping people away. Whether there's anything to do or not, ¯_(ツ)_/¯ But I have seen some people suggesting a documentation wiki of some sort, to supplement the existing docs, with a focus on HOWTOs, FAQs, etc. It even sounds like people would contribute. To me feels like it could be a good first step... even I'm more likely to put together some sort of HOWTO aimed at helping address the frequent friction points I see in the chat room than I am to make minor PRs to API docs that are mostly decent.
