Hacker News Reader

Is this scenario better managed in other language projects?

I've made contributions to Rust repos and it was a great experience, they helped me along and were very quick with responses. I never even considered it for Go because the community shot down every idea I had.

I'm a maintainer of some smaller open source projects -- you have to consider it from the project owner's point of view. To say they "shoot down ideas" is a negative way of saying it, but from their point of view they're carefully selecting and designing features and code that fit the design philosophy of the language. If the Go developers included every idea that users submitted (and there are many! -- I read the mailing lists), the language and standard libraries would be a sprawling and incoherent pile.

I imagine it varies wildly based on the project. How any other project behaves doesn't change the experience of working with the go project.

Comparing go to itself, I feel like they've lost some steam and are coping with the ecosystem steadily growing. I can't say for sure if that's the case, and I can have a lot of empathy for anyone just feeling exhausted all the time these days. That doesn't change the experience on the trying-to-contribute side of the interaction though.

Reply on news.ycombinator.com