4 ms·

Go 1.1 Beta 2 Released

70 points by voidlogic 14y ago

voidlogic 14y ago
Some important Go run-time bugs fixed since beta 1: runtime: fix deadlock in network poller runtime: make CgoMal alloc field void* runtime: change Note from union to struct runtime: change Lock from union to struct runtime: replace unions with structs runtime: replace union in MHeap with a struct runtime: reset dangling typed pointer runtime: reset typed dangling pointer
melling 14y ago
Only 23 open issues: http://swtch.com/~rsc/go11.html http://swtch.com/~rsc/go11.html
meerita 14y ago
I'm really interested in finding some articles about Go language and its main differences with others, for non-programmers i mean. May it enter on the same league as Haskell, Erlang?
- voidlogic 14y ago
  Well it is high performance like Haskell and has easy concurrency like Erlang, but both of those languages are considered by many to be hard to read and write without a lot of ramp up time. Go is very easy for anyone familiar with a C family language to write and read and tends to have very straight forward and maintainable code.
  - meerita 14y ago
    many thanks to you both :)
  - meerita 14y ago
    After watching the presentation of GO what I understand that it's more about the sintaxis reduction and being practical as much as the programmer can when writing code as well, of course, many other things. But Go seems to be the perfect language to write and maintain projects.
- baghali 14y ago
  I would highly suggest watching Rob Pike's [1] talks [2] on youtube about Go. [1] http://en.wikipedia.org/wiki/Rob_Pike http://en.wikipedia.org/wiki/Rob_Pike [2] http://www.youtube.com/results?search_query=Rob+Pike&oq=Rob+Pike&gs_l=youtube.3..0l7j0i5.1280.2932.0.3165.8.8.0.0.0.0.99.487.8.8.0...0.0...1ac.1.h_DIXz5DiEE http://www.youtube.com/results?search_query=Rob+Pike&oq=...
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 ago
  Weekly 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 ago
    Hmm, 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 ago
  The 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 ago
    Sounds like a plan, hopefully stable in the PPA will be updated to 1.1 soonish, thanks.
- georgemcbay 14y ago
  I'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.

70 points by voidlogic 14y ago

Some important Go run-time bugs fixed since beta 1: runtime: fix deadlock in network poller runtime: make CgoMal alloc field void* runtime: change Note from union to struct runtime: change Lock from union to struct runtime: replace unions with structs runtime: replace union in MHeap with a struct runtime: reset dangling typed pointer runtime: reset typed dangling pointer

melling 14y ago

Only 23 open issues: http://swtch.com/~rsc/go11.html http://swtch.com/~rsc/go11.html

meerita 14y ago

I'm really interested in finding some articles about Go language and its main differences with others, for non-programmers i mean. May it enter on the same league as Haskell, Erlang?

voidlogic 14y ago
Well it is high performance like Haskell and has easy concurrency like Erlang, but both of those languages are considered by many to be hard to read and write without a lot of ramp up time. Go is very easy for anyone familiar with a C family language to write and read and tends to have very straight forward and maintainable code.
- meerita 14y ago
  many thanks to you both :)
- meerita 14y ago
  After watching the presentation of GO what I understand that it's more about the sintaxis reduction and being practical as much as the programmer can when writing code as well, of course, many other things. But Go seems to be the perfect language to write and maintain projects.
baghali 14y ago
I would highly suggest watching Rob Pike's [1] talks [2] on youtube about Go. [1] http://en.wikipedia.org/wiki/Rob_Pike http://en.wikipedia.org/wiki/Rob_Pike [2] http://www.youtube.com/results?search_query=Rob+Pike&oq=Rob+Pike&gs_l=youtube.3..0l7j0i5.1280.2932.0.3165.8.8.0.0.0.0.99.487.8.8.0...0.0...1ac.1.h_DIXz5DiEE http://www.youtube.com/results?search_query=Rob+Pike&oq=...

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 ago
Weekly 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 ago
  Hmm, 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 ago
The 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 ago
  Sounds like a plan, hopefully stable in the PPA will be updated to 1.1 soonish, thanks.
georgemcbay 14y ago
I'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.