3 ms·
If I'm using it for hobby projects on my local machine, should I be using stable, weekly or tip? I'm guessing stable will be fine after 1.1 is pushed there (whi
by StavrosK 14y ago
If I'm using it for hobby projects on my local machine, should I be using stable, weekly or tip? I'm guessing stable will be fine after 1.1 is pushed there (which sounds like it'll be soon)?
- dmit 14y agoWeekly releases were a thing before Go hit 1.0. Right now your choice is between 1.0.3 (current stable), 1.1-beta2 and tip. I'd go with the beta if you want precompiled binaries, or tip if you don't mind the 2 minutes it takes to compile the Go toolchain and standard libraries yourself.
- StavrosK 14y agoHmm, odd, I see stable, weekly and tip on the PPA. I'll just wait for 1.1 to hit stable, it should be enough for hobbies, thanks.
- voidlogic 14y agoThe improvements in tip can be very important for large applications (for example in some HTTP realted benchmarks tip is 20-40% faster), tip also has better garbage collection leading to lower memory use. Tip also supports around 128 GB of heap on Linux/amd64 versus 8 GB for stable. All that being said, if you are just writing small programs on your machine using 1.0.3 until 1.1 is out is probably not a big deal. Just don't judge Go on performance until 1.1
- StavrosK 14y agoSounds like a plan, hopefully stable in the PPA will be updated to 1.1 soonish, thanks.
- georgemcbay 14y agoI've just been using tip post-1.0.3 and pulling down a new version and recompiling (which only takes a couple of minutes) approximately weekly. ARM support at 1.0.3 was pretty iffy and now it is really quite good. YMMV depending upon platform and how you are using Go, but in my experience tip is incredibly stable most of the time, certainly stable enough for hobby project development.