5 ms·

Go 1.16 Beta 1

86 points by mnouquet 6y ago

latchkey 6y ago
The new embed api is nice and simple! I've been using packr2 most recently, but I've been wanting this as part of the core for ages now. It makes having things like a default base configuration as a json file a lot easier.
- tmaly 6y ago
  I think the embed will be super useful. I use to use a older 3rd party package for this.
  - qz2 6y ago
    Yeah this is going to be a massive win for shipping resource dependencies. Genuine single file static linked applications is such a massive win for deployment and management.
- jlelse 6y ago
  That's a great idea to include default configuration as a file instead of coded values!
  - latchkey 6y ago
    Thanks! Yea, I built a whole kind of config api for another project a long time ago and used this technique. It worked well. That said, I went a bit overboard on it because I wanted to load a json file as the 'default' base and then be able to save it on the filesystem, update it via a http API and merge in changes over time to the saved version on disk. The reason was that this 'agent' ran on thousands of little computers (litecoin mining machines) and needed to be configurable per miner. This is the source if you want to take a look: https://github.com/blockassets/bam_agent/blob/master/service/agent/config.go https://github.com/blockassets/bam_agent/blob/master/service... It is all unit tested too. For another more recent project that isn't open source, I've since re-done it to be a lot simpler (and moved to packr2). It just reads the file. =)
  - deleted 6y ago
    [deleted]
benhoyt 6y ago
The release notes (linked) are the interesting part: https://tip.golang.org/doc/go1.16 https://tip.golang.org/doc/go1.16
ogre_codes 6y ago
Looks like Apple M1 support is live in this version: > Go 1.16 adds support of 64-bit ARM architecture on macOS (also known as Apple Silicon) with GOOS=darwin, GOARCH=arm64. A bit ahead of what I think most people expected. This should accelerate a few other projects progress. (Docker being the big one)
- AsyncAwait 6y ago
  https://www.docker.com/blog/download-and-try-the-tech-preview-of-docker-desktop-for-m1 https://www.docker.com/blog/download-and-try-the-tech-previe...
  - ogre_codes 6y ago
    From that link: > The Go language will support Apple Silicon in their 1.16 release which is targeted for February 2021. That article is a big part of why I said this was a bit earlier than expected. This ticks off one of the concerns Docker devs had about the next version.
- intricatedetail 6y ago
  That's interesting. I wonder if Apple paid contributors for M1 support. It is a closed eco-system so basically they have done what Apple should contribute if they think they still embrace developers, so I hope they paid them adequately. On the other hand it's a shame that developers spend their time on this rather than other things that could benefit the wider audience rather than just users of M1. It is just my opinion.
  - deleted 6y ago
    [deleted]
  - ogre_codes 6y ago
    It's likely Google paid for Go's M1 port, because Go is Google's language. Apple has supported some OSS projects via hardware donations, I'm not sure if Go benefitted, but Docker has. I'm not sure why you think the M1 is any more closed than Intel. It's a CPU core owned by a corporation. You can't license either design for personal or commercial use. If you are using x86 you are lining Intel's pockets (and likely Microsoft's). If you are using M1, you are lining Apple's pockets.
Groxx 6y ago
I'm always excited for new Vet additions: https://tip.golang.org/doc/go1.16#vet https://tip.golang.org/doc/go1.16#vet >The vet tool now warns about invalid calls to the testing.T method Fatal from within a goroutine created during the test. I've seen this happen a fair number of times, often discovered weeks/months after it was introduced. Good to see it's being warned about now.
kevlar1818 6y ago
I'm excited about io/fs[1]. As a newcomer to Go, one of my favorite things is the excellent I/O interfaces. I can write code to take io.Writer's or io.Reader's (etc.) and my program is suddenly both a CLI app, a Web app, and a Whatever app with minimal effort. (The effect is similar at lower levels too. For example, I can log to a file or to memory with a one-line change.) I sense a lot of potential in applying this interface-based design on filesystems themselves. [1]: https://tip.golang.org/pkg/io/fs/ https://tip.golang.org/pkg/io/fs/
- latchkey 6y ago
  Reading the API, I wonder how they plan to cancel long running (blocking) tasks, like WalkDir.
  - collinvandyck76 6y ago
    Since there's no context in the API, you'd probably just need to use a WalkDirFunc with a closure that can reach the context. Awkward for sure.
    - latchkey 6y ago
      I was referring to io outside of the WalkDirFunc. ;-)
  - jitl 6y ago
    Instantiate the FS with a context, instead of requiring a context for each kind of FS operation.
mmgutz 6y ago
Yay for `GO111MODULE=on` as default. I always had to google the name of that environment var. I remember the community backlash against go modules but that all has but faded. Packages are easier to install in this release with the version qualifier.
zimpenfish 6y ago
Annoyingly, the `go get golang.org/dl/go1.16beta1` installation method doesn't work on ApSi even if you already have an ApSi-supporting version (+edf60be151) installed. But the tar.gz for darwin/arm64 works perfectly.
rad_gruchalski 6y ago
The embed stuff is sweet.

86 points by mnouquet 6y ago

The new embed api is nice and simple! I've been using packr2 most recently, but I've been wanting this as part of the core for ages now. It makes having things like a default base configuration as a json file a lot easier.

tmaly 6y ago
I think the embed will be super useful. I use to use a older 3rd party package for this.
- qz2 6y ago
  Yeah this is going to be a massive win for shipping resource dependencies. Genuine single file static linked applications is such a massive win for deployment and management.
jlelse 6y ago
That's a great idea to include default configuration as a file instead of coded values!
- latchkey 6y ago
  Thanks! Yea, I built a whole kind of config api for another project a long time ago and used this technique. It worked well. That said, I went a bit overboard on it because I wanted to load a json file as the 'default' base and then be able to save it on the filesystem, update it via a http API and merge in changes over time to the saved version on disk. The reason was that this 'agent' ran on thousands of little computers (litecoin mining machines) and needed to be configurable per miner. This is the source if you want to take a look: https://github.com/blockassets/bam_agent/blob/master/service/agent/config.go https://github.com/blockassets/bam_agent/blob/master/service... It is all unit tested too. For another more recent project that isn't open source, I've since re-done it to be a lot simpler (and moved to packr2). It just reads the file. =)
- deleted 6y ago
  [deleted]

benhoyt 6y ago

The release notes (linked) are the interesting part: https://tip.golang.org/doc/go1.16 https://tip.golang.org/doc/go1.16

ogre_codes 6y ago

Looks like Apple M1 support is live in this version: > Go 1.16 adds support of 64-bit ARM architecture on macOS (also known as Apple Silicon) with GOOS=darwin, GOARCH=arm64. A bit ahead of what I think most people expected. This should accelerate a few other projects progress. (Docker being the big one)

AsyncAwait 6y ago
https://www.docker.com/blog/download-and-try-the-tech-preview-of-docker-desktop-for-m1 https://www.docker.com/blog/download-and-try-the-tech-previe...
- ogre_codes 6y ago
  From that link: > The Go language will support Apple Silicon in their 1.16 release which is targeted for February 2021. That article is a big part of why I said this was a bit earlier than expected. This ticks off one of the concerns Docker devs had about the next version.
intricatedetail 6y ago
That's interesting. I wonder if Apple paid contributors for M1 support. It is a closed eco-system so basically they have done what Apple should contribute if they think they still embrace developers, so I hope they paid them adequately. On the other hand it's a shame that developers spend their time on this rather than other things that could benefit the wider audience rather than just users of M1. It is just my opinion.
- deleted 6y ago
  [deleted]
- ogre_codes 6y ago
  It's likely Google paid for Go's M1 port, because Go is Google's language. Apple has supported some OSS projects via hardware donations, I'm not sure if Go benefitted, but Docker has. I'm not sure why you think the M1 is any more closed than Intel. It's a CPU core owned by a corporation. You can't license either design for personal or commercial use. If you are using x86 you are lining Intel's pockets (and likely Microsoft's). If you are using M1, you are lining Apple's pockets.

Groxx 6y ago

I'm always excited for new Vet additions: https://tip.golang.org/doc/go1.16#vet https://tip.golang.org/doc/go1.16#vet >The vet tool now warns about invalid calls to the testing.T method Fatal from within a goroutine created during the test. I've seen this happen a fair number of times, often discovered weeks/months after it was introduced. Good to see it's being warned about now.

kevlar1818 6y ago

I'm excited about io/fs[1]. As a newcomer to Go, one of my favorite things is the excellent I/O interfaces. I can write code to take io.Writer's or io.Reader's (etc.) and my program is suddenly both a CLI app, a Web app, and a Whatever app with minimal effort. (The effect is similar at lower levels too. For example, I can log to a file or to memory with a one-line change.) I sense a lot of potential in applying this interface-based design on filesystems themselves. [1]: https://tip.golang.org/pkg/io/fs/ https://tip.golang.org/pkg/io/fs/

latchkey 6y ago
Reading the API, I wonder how they plan to cancel long running (blocking) tasks, like WalkDir.
- collinvandyck76 6y ago
  Since there's no context in the API, you'd probably just need to use a WalkDirFunc with a closure that can reach the context. Awkward for sure.
  - latchkey 6y ago
    I was referring to io outside of the WalkDirFunc. ;-)
- jitl 6y ago
  Instantiate the FS with a context, instead of requiring a context for each kind of FS operation.

mmgutz 6y ago

Yay for `GO111MODULE=on` as default. I always had to google the name of that environment var. I remember the community backlash against go modules but that all has but faded. Packages are easier to install in this release with the version qualifier.

zimpenfish 6y ago

Annoyingly, the `go get golang.org/dl/go1.16beta1` installation method doesn't work on ApSi even if you already have an ApSi-supporting version (+edf60be151) installed. But the tar.gz for darwin/arm64 works perfectly.

rad_gruchalski 6y ago

The embed stuff is sweet.