Go 1.11 Rc1 released

#1

Post by soroso » Tue, Aug 14, 2018, 1:51 AM UTC

Go 1.11 Rc1 released
golang.org

Re: Go 1.11 Rc1 released

#2

Post by benesch » Tue, Aug 14, 2018, 2:56 AM UTC

Release notes are available at: https://tip.golang.org/doc/go1.11

Headline features (as judged by me) are:

* A new WebAssembly backend, js/wasm, for the gc compiler.

* Preliminary support for modules, i.e., the first step towards a package manager built into the Go command.

* Improved support for debuggers, especially Delve.

* Removal of many direct system calls from the macOS runtime. Unlike on Linux, the macOS system call interface is not considered stable. Go 1.11 binaries are now less likely to break when you upgrade your macOS version because system calls are made through the proper channel (libc).

Re: Go 1.11 Rc1 released

#3

Post by kjeetgill » Tue, Aug 14, 2018, 2:57 AM UTC

To get a test of what's actually in the release candidate check out https://github.com/golang/go/milestone/62

A lot of new stuff with the new go modules work including vgo and some interesting wasm work.

Re: Go 1.11 Rc1 released

#4

Post by shawn » Tue, Aug 14, 2018, 3:02 AM UTC

Go is still one of the most difficult and counter intuitive build systems ever devised. Usually you’d expect a project to build out of the box. Go seems to take a stance of “Haha nope, get ready to figure out which version of the standard library this 4 month old project was written against, then have fun trying to update it to the latest.”

I like the language though. Their green threads are still the best.

Re: Go 1.11 Rc1 released

#5

Post by alyandon » Tue, Aug 14, 2018, 3:06 AM UTC

shawn wrote: post #4

Go is still one of the most difficult and counter intuitive build systems ever devised. Usually you’d expect a project to build out of the box. Go seems to take a stance of “Haha nope, get ready to figure out which version of the standard library this 4 month old project was written against, then have fun trying to update it to the latest.” I like the language though. Their green threads are still the best.

For what it is worth, I agree 100% and dependency management tools like Glide have been indispensable for me.

Re: Go 1.11 Rc1 released

#6

Post by pknopf » Tue, Aug 14, 2018, 3:13 AM UTC

shawn wrote: post #4

Go is still one of the most difficult and counter intuitive build systems ever devised. Usually you’d expect a project to build out of the box. Go seems to take a stance of “Haha nope, get ready to figure out which version of the standard library this 4 month old project was written against, then have fun trying to update it to the latest.” I like the language though. Their green threads are still the best.

> Go is still one of the most difficult and counter intuitive build systems ever devised.

I'm currently working on building all the coreclr/corefx repos for .NET Core. Their build system is incredibly convoluted.

Re: Go 1.11 Rc1 released

#7

Post by [deleted] » Tue, Aug 14, 2018, 3:18 AM UTC

shawn wrote: post #4

Go is still one of the most difficult and counter intuitive build systems ever devised. Usually you’d expect a project to build out of the box. Go seems to take a stance of “Haha nope, get ready to figure out which version of the standard library this 4 month old project was written against, then have fun trying to update it to the latest.” I like the language though. Their green threads are still the best.

[deleted]

Re: Go 1.11 Rc1 released

#8

Post by irfansharif » Tue, Aug 14, 2018, 3:20 AM UTC

shawn wrote: post #4

Go is still one of the most difficult and counter intuitive build systems ever devised. Usually you’d expect a project to build out of the box. Go seems to take a stance of “Haha nope, get ready to figure out which version of the standard library this 4 month old project was written against, then have fun trying to update it to the latest.” I like the language though. Their green threads are still the best.

From Go's 1.0 compatibility guarantee[0]:

> It is intended that programs written to the Go 1 specification will continue to compile and run correctly, unchanged, over the lifetime of that specification. [...] Go programs that work today should continue to work even as future "point" releases of Go 1 arise (Go 1.1, Go 1.2, etc.).

I've found this to be upheld in practice, especially so for the standard library. I have yet to come across a case where I was concerned with which "version" of the standard library some project was written against. Are you perhaps talking about non-stdlib packages?

[0]: https://golang.org/doc/go1compat

Re: Go 1.11 Rc1 released

#9

Post by mlevental » Tue, Aug 14, 2018, 3:21 AM UTC

does it have generics yet? yes I'm sure someone will call me a troll.

Re: Go 1.11 Rc1 released

#10

Post by Walkman » Tue, Aug 14, 2018, 3:28 AM UTC

shawn wrote: post #4

Go is still one of the most difficult and counter intuitive build systems ever devised. Usually you’d expect a project to build out of the box. Go seems to take a stance of “Haha nope, get ready to figure out which version of the standard library this 4 month old project was written against, then have fun trying to update it to the latest.” I like the language though. Their green threads are still the best.

Can you tell at least one specific example where they broke the standard library?