When I do a search, 9 out of 10 questions that are useful to me were closed as off topic. Fortunately they are not deleted. I confirm also the bias toward new users: I once registered to provide an answer which was missing to a question. Someone, an older user, modified my answer and deleted a part of it, so it then looked rather dumb. Obviously it was downvoted. I never came back.
Yes, that's a problem: Old users with high reputation abusing their power to edit other people's questions and answers.
Personally, I find it distasteful when somebody other than the question or answer's original author makes a substantial edit. Edits by third parties ought to be to fix typos, fix bad code formatting, improve clarity and the like.
One of the main points of the editing system is to fix the biggest problem with Q&A sites before SO - outdated information. Editing other's posts means that content can get updated, even if the original poster isn't around to curate it.
Everyone I've heard hating on StackOverflow are people asking or answering, who have ownership over their questions and dislike the rules or way the site works. The reality is that SO knows 99% of it's users never register and are reading answers, not asking or answering questions.
The reason SO is a great resource is that the rules create an environment that doesn't allow cruft to build. Yes, that puts off some people, that's a worthy trade in my mind. I'd rather have good content than more content.
But you are lucky if your project has a large group of programmers. There is more probably a large group of projects with a small group of programmers. There are also some large projects: Linux, KDE, LibreOffice, VLC, LLVM, etc... and none is written in Go.
>LibreOffice (based on StarOffice, 6.0 released in 2002)
I think you have a point r.e there being more smaller projects than large projects with large teams. But this is a terrible argument. Go was released in 2007. Are you being facetious or are you suggesting that porting a mature codebase to Go is that easy? CoreOS was released in 2013 and so was Docker. I know that Docker actually ported to Go after the fact, but it was still relatively young and Go was already mature by then.
There is also the sourceforge example. Since they can not make enough money with ads on the site to survive, they put them in the archives. They will die also at the end, but a lot of projects with them.
I have carefully compared the two languages and I do not see more similarity than between Go and Swift or any other language. You have yourself cited the different memory management models, and this is the main characteristic of Rust. The sole common feature is the use of LLVM.