home | list info | list archive | date index | thread index

if starting with Go, any reason not to go straight to Go 1.13?

  • Subject: if starting with Go, any reason not to go straight to Go 1.13?
  • From: "Robert P. J. Day" <rpjday [ at ] crashcourse [ dot ] ca>
  • Date: Tue, 20 Aug 2019 10:14:16 -0400 (EDT)
  friend of mine asks, if one's company is getting ready to start
using Go for a brand new project, and official start is still at least
a couple months away, is there any reason to not wait for Go 1.13
(allegedly due out shortly), and start with that?

  i've been playing with Go 1.12.7 on my fedora system, and have done
enough reading to note some significant differences (particularly
module mode and the deprecation of GOPATH, which is a pretty big
change).

  also, the schedule is that Go 1.13 is supposed to be out officially
in a couple of weeks, so that wouldn't even represent much of a delay
(if any).

  so, Go programmers, thoughts? if the people on this project aren't
Go programmers yet, any reason not to just start with Go 1.13?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                         http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

To unsubscribe send a blank message to linux+unsubscribe [ at ] linux-ottawa [ dot ] org
To get help send a blank message to linux+help [ at ] linux-ottawa [ dot ] org
To visit the archives: https://lists.linux-ottawa.org