Re: [linux] if starting with Go, any reason not to go straight to Go 1.13?
On Tue, 20 Aug 2019, Rick Leir wrote: > In my experience with software businesses, when you have a new > project you want it finished by yesterday. The programmer in me says > the first cut at the code will get thrown out or should be. Even if > you were talking of python 2.7 and 3.0 I would say get started and > plan for a possible upgrade ( which might never happen, business > considerations often dictate staying with the existing or previous > version). > YMMV -- Rick i understand the logic, but recall that the project i'm talking about won't start for at least another month or two, so there's no frantic rush to start coding right now. given that scenario, and the apparently significant improvements coming with Go 1.13, the question remains. rday To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org To get help send a blank message to linux+h...@linux-ottawa.org To visit the archives: https://lists.linux-ottawa.org
Re: [linux] if starting with Go, any reason not to go straight to Go 1.13?
In my experience with software businesses, when you have a new project you want it finished by yesterday. The programmer in me says the first cut at the code will get thrown out or should be. Even if you were talking of python 2.7 and 3.0 I would say get started and plan for a possible upgrade ( which might never happen, business considerations often dictate staying with the existing or previous version). YMMV -- Rick On August 20, 2019 10:14:16 AM EDT, "Robert P. J. Day" wrote: > > 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+unsubscr...@linux-ottawa.org >To get help send a blank message to linux+h...@linux-ottawa.org >To visit the archives: https://lists.linux-ottawa.org -- Sorry for being brief. Alternate email is rickleir at yahoo dot com
[linux] if starting with Go, any reason not to go straight to Go 1.13?
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+unsubscr...@linux-ottawa.org To get help send a blank message to linux+h...@linux-ottawa.org To visit the archives: https://lists.linux-ottawa.org
