Go 1.11 Rc1 released

Release notes are available at: <a href="https:&#x2F;&#x2F;tip.golang.org&#x2F;doc&#x2F;go1.11" rel="nofollow">https:&#x2F;&#x2F;tip.golang.org&#x2F;doc&#x2F;go1.11</a><p>Headline features (as judged by me) are:<p>* A new WebAssembly backend, js&#x2F;wasm, for the gc compiler.<p>* Preliminary support for modules, i.e., the first step towards a package manager built into the Go command.<p>* Improved support for debuggers, especially Delve.<p>* 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).

To get a test of what&#x27;s actually in the release candidate check out <a href="https:&#x2F;&#x2F;github.com&#x2F;golang&#x2F;go&#x2F;milestone&#x2F;62" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;golang&#x2F;go&#x2F;milestone&#x2F;62</a><p>A lot of new stuff with the new go modules work including vgo and some interesting wasm work.

Extremely relevant: We need to talk about Go modules <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=7GGr3S41gjM" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=7GGr3S41gjM</a>

There has been some tremendous improvements for ARM architecture. If you run some serious code on raspberry PIs, get ready to be amazed.

What is the current recommendation for dependency management in Go for a new project?

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.”<p>I like the language though. Their green threads are still the best.