I'm not suggesting anyone improve anything. I'm just trying to point out that, if there are doc complainers, it is because there is an actual barrier, and that barrier is almost certainly keeping people out of the tent that you want in the tent.
I don't think the doc for getAppFileName is _confusing_ per se, it just doesn't have sufficient detail on semantics to be sure what the output is going to be before trying it out. So it leads to surprises. Not a big one, but if there are a lot of little things like that, you end up with people feeling "death by 1000 paper cuts". Personally, I don't need any more docs, and I'm cut from very similar cloth that I don't want to spend an undue amount of time writing excessive amounts of documentation. But I think if there are adoption goals, then it's good to think about what the barriers to adoption really are, and try to figure out how it might get resourced. Seems like if someone's got a good vision for what would be helpful, there are people who might contribute if encouraged, but I could be wrong there. However, the impression that I'm getting as someone new to the community is that, even if people were to step up to the plate, it's not clear the core team is all that receptive. That's why I thought it was important to share my views, because I work with people who absolutely won't touch Nim because of the docs, and they are incredibly smart programmers who, for instance, don't find Rust "too complicated" as many people do. They're not the kind of people to come here and complain about lack of docs, they're just going to decide it's not worth the extra effort, and not show up at all.
