3 ms·
"Tip Or Don't Bother" This is pretty true, although I would not bother using tip if writing a small command line utility or learning Go, but for a large projec
by voidlogic 14y ago
"Tip Or Don't Bother"
This is pretty true, although I would not bother using tip if writing a small command line utility or learning Go, but for a large project this is good advice. Execution time and memory usage are greatly improved in tip, at the cost you might run into bug that has not been fixed yet.
Here is the burn down to Go 1.1's release, when it hits bottom it releases. http://swtch.com/~rsc/go11.html# http://swtch.com/~rsc/go11.html#
Go 1.1 RC should be out in April I believe.
Also if you need to pick a Go tip build to use this is useful: http://build.golang.org/ http://build.golang.org/
- phasevar 14y agoJust how much has execution time improved? I'd love to see some benchmarks.
- voidlogic 14y agoIf you read the golang-dev google groups mailing list you will see lots of micro-benchmarks posted for specific commits. The best test is to install both stable and tip on your machine and compile your application with both. In one of my application there was a 9% improvement, in another it was 53%. When Go 1.1 is released I presume the computer benchmarks game will be updated, which might make comparison, at lease with other languages, easier.