Yes, but if your barriers to contribution exist to discourage those that's a roundabout thing that affects serious contrib too.
-
-
Replying to @ManishEarth @whitequark
If you don't like drive by PRs just close the damn things.
2 replies 0 retweets 1 like -
Replying to @ManishEarth @whitequark
(also, the dynamic of a large community maintaining code is different than solo maintainership)
1 reply 0 retweets 3 likes -
Replying to @ManishEarth @whitequark
Yeah this is key to me — once you hit Go’s scale you have enough maintainers to easily handle the random stuff with little effort
1 reply 0 retweets 2 likes -
-
Replying to @whitequark @ManishEarth
litmus check: golang/go and rust-lang/rust have almost exactly same number of forks.
1 reply 0 retweets 0 likes -
Replying to @whitequark
IIRC go has a larger paid team. I think Rust has hit the scale @Gankro is talking about, I am not sure if Rust has hit/surpassed Go.
1 reply 0 retweets 0 likes -
Replying to @ManishEarth
Rust is an interesting case because I'm pretty sure I'll never contribute even trivial stuff to rustc or libstd.
2 replies 0 retweets 0 likes -
Replying to @whitequark
why not? is it the process? what can we do to improve it?
1 reply 0 retweets 0 likes -
Replying to @ManishEarth
incredibly long local builds; even more incredibly long bots; all the random bot failures; PRs getting kicked down the road for weeks
4 replies 0 retweets 4 likes
First time I tried Go I found a runtime bug. Known for months. No fix. Debugged it. My fix got kicked around for a *month*. Gave up on Go.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.