A new Go API for Protocol Buffers

Re:A new Go API for Protocol Buffers by neild on Monday March 02, 2020 @05:01PM (#22469506)

Indeed, tying the name of a package to a hosting provider is a bad idea! That's why we changed to an import path which isn't tied to one. google.golang.org/protobuf is not tied to any particular provider, and we can redirect it wherever we want.

See "go help importpath" for details on how this works.

[ Parent | on HN ]

Re:A new Go API for Protocol Buffers by randallsquared on Monday March 02, 2020 @10:09PM (#22471460)

> - Confusing: google.golang.org/protobuf@v1 doesn't exist, but v2 does.

> google.golang.org/protobuf is not tied to any particular provider, and we can redirect it wherever we want.

I agree, this is confusing. Why doesn't google.golang.org/protobuf@v1 return what's at github.com/golang/protobuf, then, if only to provide a tidy answer for those who wonder what v1 looked like?

[ Parent | on HN ]

Re:A new Go API for Protocol Buffers by tsimionescu on Tuesday March 03, 2020 @02:54AM (#22472665)

Because the Go package name is github.com/golang/protobuf. Serving it from a different address is already a breaking change.

[ Parent | on HN ]