Re:Playing with Go1.1beta2, it's much faster
by jgrahamc on Tuesday April 09, 2013 @03:22AM
(#5516862)
It's a pity this is a comparison with Go 1.0.3. That's so old as to be a almost useless comparison given that everyone who's serious about Go uses something from the hg repository.
[ Parent
| on HN ]
Re:Playing with Go1.1beta2, it's much faster
by laumars on Tuesday April 09, 2013 @03:55AM
(#5516928)
1.0.3 was the last stable release. 1.1 is the next stable release. Not everyone feels confident running testing repos for production systems (even if they are reported to be stable)
Re:Playing with Go1.1beta2, it's much faster
by trailfox on Tuesday April 09, 2013 @03:35AM
(#5516890)
Those serious about Go are running (production?) systems using pre-release builds? Is that a common practice?
Re:Playing with Go1.1beta2, it's much faster
by enneff on Tuesday April 09, 2013 @04:16AM
(#5516975)
It's not very common. John (the GP) uses the Go bleeding edge at CloudFlare because he needs some of the recent improvements. To do this, he really needs to know what he's doing (and he does). Typical Go users just use the stable branch.
Re:Playing with Go1.1beta2, it's much faster
by voidlogic on Tuesday April 09, 2013 @09:54AM
(#5518027)
I know of two more Go heavy start-ups and one large company that also use tip.
Yeah, especially now that the tip is Go 1.1 post-beta.
It's pretty common in any language that's seeing significant development, targeting a version that's not going to be too long in the tooth by the time you want to go to production.