@Stefan_Salewski: > No, there is nothing wrong with them. Maybe moron is not a good term -- I > just recently learned that term, maybe Araq taught me.
Lesson: Don't use words or phrases you don't know well. :-D If in doubt, look up words in a dictionary. I do this all the time, even if I'm "relatively" sure I'm using the right word. If you think you have _almost_ the right word, use a thesaurus. :-) > But the fact is that already a few of such unskilled people who refuse to > read books or tutorials [...] I assume in most cases it's not really "refusing", but that people just assume (not even consciously) that the resources are there to answer questions, even relatively simple ones. Maybe the Nim community seems bigger that it actually is. > IRC logs where full of such questions in the last months, I stopped reading. I think that's actually a good thing. Not directly, but I'd say it at least suggests that more people get interested in Nim and try it out. @cblake: > Something neglected in this analysis is that as the community grows, the core > devs will not need to answer (basic) questions as much. As long as growth is > broad-spectrum skills-wise, mid-skills people can pick up that effort. Fully agreed. Even I answer questions sometimes if I think I'm qualified. :-) One other thing: Maybe we need more/better documentation we can point people to for FAQs? That may reduce the questions on IRC somewhat, and even if questions come, we can point to the documentation. Maybe it's possible to extend disruptek's bot so that people can just give the bot some keyword(s) so the bot prints a link to the appropriate documentation? By the way, as far as questions on IRC are concerned, it's not enough to point people to books or article series. I can completely understand that nobody wants to read a lot of documentation when they're just finding out if the language is for them. I know some people _do_ read lots of docs beforehand (I did), but on average I don't think we should "require" it. @Stefan_Salewski: > And another important point for more users would be a weekly blog reporting > news about developing and also about some internals. Yes, a regular blog post would be great. It doesn't have to be weekly (although that would be nice, if there's enough to say). For example, I like reading the Sourcehut updates ([example](https://lists.sr.ht/~sircmpwn/sr.ht-announce/%3CC4YIQ6CIJUNR.VET9MUHZE9GO%40homura%3E)). When I got into Nim, I liked the survey results post, but having a blog post only once or twice a year is too little for a sense of progress.
