On Sun, Jun 25, 2017 at 4:36 PM Christoph Berger < christoph.g.ber...@gmail.com> wrote:
> Thanks to the Go 1 Compatibility Promise, it was never a problem for me to > always use the latest Go version (via Homebrew, BTW, which keeps my Go > installation up-to-date with next-to-zero effort). > > That was my first hunch as well, but language compatibility doesn't automatically guarantee implementation compatibility. I'll definitely agree one should strive to make the code work well with the newest Go release always, but there are reasons people doesn't upgrade right away. Reproducible builds is common nowadays and that requires you use the same version of the Go compiler, for instance. What I tend to do is to use the newest release for building the software (this ensures that the eventual upgrade path is clear). And then let a build system handle the older versions if needed. That way, you can often program yourself out of the problem by mangling PATHs rather than running a complete docker installation. On the other hand, if you do containerize your world anyhow, that may be the simplest solution. I'm quite partial to either jails (FreeBSD) or Zones (Solaris/Illumos) personally over docker though. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
