#golang
#golang
How I think about it is as a way to deflake tests by simulating an infinitely fast processor (because time doesn’t move until all work is done), and then shorten them by compressing time (because time jumps once it moves).
📝 Release notes: https://go.dev/doc/go1.25
⬇️ Download: https://go.dev/dl/#go1.25.0
#golang
How I think about it is as a way to deflake tests by simulating an infinitely fast processor (because time doesn’t move until all work is done), and then shorten them by compressing time (because time jumps once it moves).
FIPS 140, like it or not, is often a requirement, and I was increasingly sad about large deployments replacing the Go crypto packages with non-memory safe cgo bindings.
Go is now one of the easiest and most secure ways to build under FIPS 140.
FIPS 140, like it or not, is often a requirement, and I was increasingly sad about large deployments replacing the Go crypto packages with non-memory safe cgo bindings.
Go is now one of the easiest and most secure ways to build under FIPS 140.
Senior engineers putting in the work and giving no-bullshit perspectives.
Read this one by @crawshaw.io through. Not skim or half. Especially if you are a skeptic.
Senior engineers putting in the work and giving no-bullshit perspectives.
Read this one by @crawshaw.io through. Not skim or half. Especially if you are a skeptic.