5 ms·

> the tedium of dealing with the unwashed masses -- typical NIH syndrome If you've managed a large OSS project with a wide userbase before, you know how annoyi

> the tedium of dealing with the unwashed masses -- typical NIH syndrome If you've managed a large OSS project with a wide userbase before, you know how annoying it can be to deal with large numbers of repetitive requests from folks who don't have the full context of what's going on in the project. It's time consuming at best, and at worse some small minority of those folks take up a toxic attitude that sucks the happiness out of your work. There's no need to accuse maintainers of arrogance or NIH syndrome. This stuff is hard, and we all try to do the best we can.

0815test 7y ago
> ...repetitive requests from folks who don't have the full context of what's going on in the project Write some FAQ's, so that people are made aware of that context. An openly-developed project can actually be very successful at dealing with this, because pointing folks to the centralized discussion in which the pros and cons of commonly-requested feature X are dealt with becomes second nature after a while. We saw an example of this very recently with the surprisingly-mild brouhaha about Rust's choice of a postfix .await syntax.
- Carpetsmoker 7y ago
  There's an FAQ: https://golang.org/doc/faq https://golang.org/doc/faq For generics specifically, there's a "Summary of Go Generics Discussions", which is quite comprehensive: https://docs.google.com/document/d/1vrAy9gMpMoS3uaVphB32uVXX4pi-HnNjkMEgyAHX4N4/view#heading=h.vuko0u3txoew https://docs.google.com/document/d/1vrAy9gMpMoS3uaVphB32uVXX...
- unionpivo 7y ago
  From my experience as oss developer on several different projects (small to medium ones),a lot of people don't bother to read FAQ's. There are some people that hit the problem, start googling, and trying to find information, and some that just fire off email or stack overflow question (often so badly, you need several back and forth)

0815test 7y ago

> ...repetitive requests from folks who don't have the full context of what's going on in the project Write some FAQ's, so that people are made aware of that context. An openly-developed project can actually be very successful at dealing with this, because pointing folks to the centralized discussion in which the pros and cons of commonly-requested feature X are dealt with becomes second nature after a while. We saw an example of this very recently with the surprisingly-mild brouhaha about Rust's choice of a postfix .await syntax.

Carpetsmoker 7y ago
There's an FAQ: https://golang.org/doc/faq https://golang.org/doc/faq For generics specifically, there's a "Summary of Go Generics Discussions", which is quite comprehensive: https://docs.google.com/document/d/1vrAy9gMpMoS3uaVphB32uVXX4pi-HnNjkMEgyAHX4N4/view#heading=h.vuko0u3txoew https://docs.google.com/document/d/1vrAy9gMpMoS3uaVphB32uVXX...
unionpivo 7y ago
From my experience as oss developer on several different projects (small to medium ones),a lot of people don't bother to read FAQ's. There are some people that hit the problem, start googling, and trying to find information, and some that just fire off email or stack overflow question (often so badly, you need several back and forth)