3 ms·
Protobuf renaming?
by solipsism 6y ago
Protobuf renaming?
- tsimionescu 6y agoI was referring to this: https://blog.golang.org/protobuf-apiv2 https://blog.golang.org/protobuf-apiv2 > The github.com/golang/protobuf module is APIv1. > The google.golang.org/protobuf module is APIv2. We have taken advantage of the need to change the import path to switch to one that is not tied to a specific hosting provider. Basically, Google realized that it's not a good idea to tie your package's identity to GitHub's URL scheme. This is easy for Google to fix, but the majority of Go packages suffer from the same problem, and it is much harder for a small project to start maintaining a DNS record that they control to point that to GitHub. Not to mention, if GitHub decided to change its URL scheme for some reason, almost all Go builds on the planet would have to change. And of course, the whole problem stems from relying on DNS to name your packages. No one wants to bother with DNS, so they go for the low effort option and let some hosting provider handle it for them, without caring what happens in 10 years time.