Last fall we announced a survey in this list about how and why breaking
changes are handled differently in 18 different software ecosystems,
including Go. We've just submitted a paper to a conference about the
results, and we've also set up a site where you can compare how different
ecosystem
Thank you both -- yes, I see the problem. It was tricky to get the
questions right to apply across ecosystems with different infrastructure
and terminology; but we're particularly interested in comparing ecosystems
like Go and (much of) Swift that don't have central repositories with ones
like
Hi, I'm looking for some help from developers who write Go packages. My
research group is interested in the different choices new package managers
and repositories are making when designing their ecosystems. Platforms like
Node.js/NPM, Google's go, and Rust/Cargo are making somewhat different
