6 ms·

Go 1.15 – Draft release notes

119 points by azhenley 6y ago

rudolph9 6y ago
I wonder how this will affect wasm targets. I’ve had relatively few errors when using a Golang wasm but depending on the project they wind up being massive! I also hate having to serve a separate js file to simuLate the Golang runtime which probably isn’t going away but smaller and more efficient would be a marked improvement!
- rudolph9 6y ago
  For reference https://github.com/golang/go/wiki/WebAssembly https://github.com/golang/go/wiki/WebAssembly
- k__ 6y ago
  Yes, it will be interesting how GC/runtime languages get along with WebAssembly in the future. At the moment everything I saw looked rather bleak.
- PhilippGille 6y ago
  Did you have a look at https://tinygo.org/webassembly/ https://tinygo.org/webassembly/ ?
  - rudolph9 6y ago
    I have! Given the compatibility of tiny go with community packages this isn’t ideal. I think if I was using this I would be building from scratch in which case I would just use rust.
andreygrehov 6y ago
Still no?
- melling 6y ago
  They said years ago not before 2.0
  - andreygrehov 6y ago
    Ah, really? My apologies then. I must've missed that.
CalmStorm 6y ago
This article [1] describes the features in 1.15. The new linker is quite impressive in reducing executable size because it reduces more unused code: For more realistic programs, binary sizes go down by 3.5% or as much as 22%. The original linker was written by Ken Thompson, who is now retired. [1] https://lwn.net/Articles/820217/ https://lwn.net/Articles/820217/
- smmnyc 6y ago
  Here is more on how they reduced the binary sizes: https://twitter.com/bradfitz/status/1256350305739915265 https://twitter.com/bradfitz/status/1256350305739915265 > Mostly https://go-review.googlesource.com/c/go/+/230544 https://go-review.googlesource.com/c/go/+/230544 and also https://go-review.googlesource.com/c/go/+/231397and https://go-review.googlesource.com/c/go/+/231397and lesser misc stuff like https://go-review.googlesource.com/c/go/+/228111 https://go-review.googlesource.com/c/go/+/228111
- fermentation 6y ago
  Ah I hadn't realized that he had retired! I assumed he'd still been working on golang.
- gen220 6y ago
  Some other minor improvements that made my shortlist: > On a Unix system, if the kill command or kill system call is used to send a SIGSEGV, SIGBUS, or SIGFPE signal to a Go program, and if the signal is not being handled via os/signal.Notify, the Go program will now reliably crash with a stack trace. In earlier releases the behavior was unpredictable. > Allocation of small objects now performs much better at high core counts, and has lower worst-case latency. Plus some usability improvements to the flag lib. I’d love to see this get closer and closer to spf13’s, taking the best and most stable parts. I love spf13’s contributions to the Go community, and a lot of these ideas deserve to be in stdlib in my view. Anyways, I love how each line item in these updates is a small and unambiguous step forward. There’s something very satisfying about tools that systematically get better with every release.
- weberc2 6y ago
  I was just measuring the size of Terraform earlier today--it's a program with 733 dependencies and it weighed in at 63 mb without stripping symbols or compressing when compiled with go 1.13. I was comparing it to our Python executable bundle that weighed in at 260mb with only 104 dependencies and had become too big to run in a lambda, and I found myself jealous of everyone who is fussing over their 10mb Go binaries. Anyway, I rebuilt Terraform and it's now I'm 6mb more jealous of everyone fussing over their Go binary sizes. EDIT: If I compress the Terraform binary and the Python lambda, they become 14mb and 250mb respectively. At least Python is fast, right?
npiit 6y ago
>Changes to the language: There are no changes to the language Golang never fails to disappoint.
conroy 6y ago
I despise Google Groups on mobile, as it usually requires me to log into my Google account. For those of you like me, the release notes[0] are easy to read in my phone. [0] https://tip.golang.org/doc/go1.15 https://tip.golang.org/doc/go1.15
- CGamesPlay 6y ago
  Mods, can we get the link updated to the actual release notes? https://tip.golang.org/doc/go1.15 https://tip.golang.org/doc/go1.15
  - dang 6y ago
    Ok, changed from https://groups.google.com/d/msg/golang-announce/A0frTIl9W6Y/mTgsOVCnAQAJ https://groups.google.com/d/msg/golang-announce/A0frTIl9W6Y/....
totalperspectiv 6y ago
Has there been any announced timeline on Go2?
- throw_m239339 6y ago
  I know one needs to refrain from being sarcastic here, but LOL. "Go2" is the typical exemple of an idea parking. It is not going to happen.
  - mseepgood 6y ago
    That's simply not true.
    - pjmlp 6y ago
      It was true for error handling improvements, which got added is just a small part of the original proposal. And despite the 2nd attempt to the contracts proposal (now one year old with little visible progress, no updates since August on public git), or the Featherweight Go presented last week, there is still no guarantee that any of that will ever land on Go.
      - RabbitmqGuy 6y ago
        As a person who uses Go i don't need day by day updates to know that the Go team is working hard on generics. I trust that they are & indeed they are. > now one year old with little visible progress, no updates since August on public git. This is untrue. In January this year the Go team wrote[1]; "Module support is in good shape and getting better with each day, and we are also making progress on the generics front (more on that later this year)." If you looked at the draft/experimental[2] branch where generics development has been taking place, you can see that it has had activity as late as just last week. In the featherweightGo presentation, Phil Wadler said Rob Pike wrote to him asking if he would be interested in working with the Go team so that they can figure out generics and try and get them right. And that is how featherweightGo came to be. So a lot has/is been happening. 1. https://blog.golang.org/go1.15-proposals https://blog.golang.org/go1.15-proposals 2. https://go-review.googlesource.com/c/go/+/187317 https://go-review.googlesource.com/c/go/+/187317 3. https://youtu.be/Dq0WFigax_c https://youtu.be/Dq0WFigax_c
zachgersh 6y ago
The GOPROXY API being either , or | makes me a tiny bit sad. Now, what was once simple, has given these characters new and not easily discernible semantic meaning. I really wish I had commented on this proposal but missed it until the feature was already in.
- ithkuil 6y ago
  What would propose as an alternative? Even if it's too late for this particular thing, I'm curious anyway as there are similar problems that crop up here and there at $dayhob
thefounder 6y ago
I hope one day they will fix the reflect.StructOf.
omginternets 6y ago
Tangentially-related: does anybody know the status of go plugins? IIRC, only Linux and Darwin are supported, but is this a permanent state of affaires? Does the Go team intend to further develop this (e.g adding support for BSD and Win)?

119 points by azhenley 6y ago

I wonder how this will affect wasm targets. I’ve had relatively few errors when using a Golang wasm but depending on the project they wind up being massive! I also hate having to serve a separate js file to simuLate the Golang runtime which probably isn’t going away but smaller and more efficient would be a marked improvement!

rudolph9 6y ago
For reference https://github.com/golang/go/wiki/WebAssembly https://github.com/golang/go/wiki/WebAssembly
k__ 6y ago
Yes, it will be interesting how GC/runtime languages get along with WebAssembly in the future. At the moment everything I saw looked rather bleak.
PhilippGille 6y ago
Did you have a look at https://tinygo.org/webassembly/ https://tinygo.org/webassembly/ ?
- rudolph9 6y ago
  I have! Given the compatibility of tiny go with community packages this isn’t ideal. I think if I was using this I would be building from scratch in which case I would just use rust.

andreygrehov 6y ago

Still no?

melling 6y ago
They said years ago not before 2.0
- andreygrehov 6y ago
  Ah, really? My apologies then. I must've missed that.

CalmStorm 6y ago

This article [1] describes the features in 1.15. The new linker is quite impressive in reducing executable size because it reduces more unused code: For more realistic programs, binary sizes go down by 3.5% or as much as 22%. The original linker was written by Ken Thompson, who is now retired. [1] https://lwn.net/Articles/820217/ https://lwn.net/Articles/820217/

smmnyc 6y ago
Here is more on how they reduced the binary sizes: https://twitter.com/bradfitz/status/1256350305739915265 https://twitter.com/bradfitz/status/1256350305739915265 > Mostly https://go-review.googlesource.com/c/go/+/230544 https://go-review.googlesource.com/c/go/+/230544 and also https://go-review.googlesource.com/c/go/+/231397and https://go-review.googlesource.com/c/go/+/231397and lesser misc stuff like https://go-review.googlesource.com/c/go/+/228111 https://go-review.googlesource.com/c/go/+/228111
fermentation 6y ago
Ah I hadn't realized that he had retired! I assumed he'd still been working on golang.
gen220 6y ago
Some other minor improvements that made my shortlist: > On a Unix system, if the kill command or kill system call is used to send a SIGSEGV, SIGBUS, or SIGFPE signal to a Go program, and if the signal is not being handled via os/signal.Notify, the Go program will now reliably crash with a stack trace. In earlier releases the behavior was unpredictable. > Allocation of small objects now performs much better at high core counts, and has lower worst-case latency. Plus some usability improvements to the flag lib. I’d love to see this get closer and closer to spf13’s, taking the best and most stable parts. I love spf13’s contributions to the Go community, and a lot of these ideas deserve to be in stdlib in my view. Anyways, I love how each line item in these updates is a small and unambiguous step forward. There’s something very satisfying about tools that systematically get better with every release.
weberc2 6y ago
I was just measuring the size of Terraform earlier today--it's a program with 733 dependencies and it weighed in at 63 mb without stripping symbols or compressing when compiled with go 1.13. I was comparing it to our Python executable bundle that weighed in at 260mb with only 104 dependencies and had become too big to run in a lambda, and I found myself jealous of everyone who is fussing over their 10mb Go binaries. Anyway, I rebuilt Terraform and it's now I'm 6mb more jealous of everyone fussing over their Go binary sizes. EDIT: If I compress the Terraform binary and the Python lambda, they become 14mb and 250mb respectively. At least Python is fast, right?

npiit 6y ago

>Changes to the language: There are no changes to the language Golang never fails to disappoint.

conroy 6y ago

I despise Google Groups on mobile, as it usually requires me to log into my Google account. For those of you like me, the release notes[0] are easy to read in my phone. [0] https://tip.golang.org/doc/go1.15 https://tip.golang.org/doc/go1.15

CGamesPlay 6y ago
Mods, can we get the link updated to the actual release notes? https://tip.golang.org/doc/go1.15 https://tip.golang.org/doc/go1.15
- dang 6y ago
  Ok, changed from https://groups.google.com/d/msg/golang-announce/A0frTIl9W6Y/mTgsOVCnAQAJ https://groups.google.com/d/msg/golang-announce/A0frTIl9W6Y/....

totalperspectiv 6y ago

Has there been any announced timeline on Go2?

throw_m239339 6y ago
I know one needs to refrain from being sarcastic here, but LOL. "Go2" is the typical exemple of an idea parking. It is not going to happen.
- mseepgood 6y ago
  That's simply not true.
  - pjmlp 6y ago
    It was true for error handling improvements, which got added is just a small part of the original proposal. And despite the 2nd attempt to the contracts proposal (now one year old with little visible progress, no updates since August on public git), or the Featherweight Go presented last week, there is still no guarantee that any of that will ever land on Go.
    - RabbitmqGuy 6y ago
      As a person who uses Go i don't need day by day updates to know that the Go team is working hard on generics. I trust that they are & indeed they are. > now one year old with little visible progress, no updates since August on public git. This is untrue. In January this year the Go team wrote[1]; "Module support is in good shape and getting better with each day, and we are also making progress on the generics front (more on that later this year)." If you looked at the draft/experimental[2] branch where generics development has been taking place, you can see that it has had activity as late as just last week. In the featherweightGo presentation, Phil Wadler said Rob Pike wrote to him asking if he would be interested in working with the Go team so that they can figure out generics and try and get them right. And that is how featherweightGo came to be. So a lot has/is been happening. 1. https://blog.golang.org/go1.15-proposals https://blog.golang.org/go1.15-proposals 2. https://go-review.googlesource.com/c/go/+/187317 https://go-review.googlesource.com/c/go/+/187317 3. https://youtu.be/Dq0WFigax_c https://youtu.be/Dq0WFigax_c

zachgersh 6y ago

The GOPROXY API being either , or | makes me a tiny bit sad. Now, what was once simple, has given these characters new and not easily discernible semantic meaning. I really wish I had commented on this proposal but missed it until the feature was already in.

ithkuil 6y ago
What would propose as an alternative? Even if it's too late for this particular thing, I'm curious anyway as there are similar problems that crop up here and there at $dayhob

thefounder 6y ago

I hope one day they will fix the reflect.StructOf.

omginternets 6y ago

Tangentially-related: does anybody know the status of go plugins? IIRC, only Linux and Darwin are supported, but is this a permanent state of affaires? Does the Go team intend to further develop this (e.g adding support for BSD and Win)?