4 ms·
On a 6-month release-cycle, how much change do you want each release? (1.13 is scheduled to be released in August, following 1.12's release in February) It's m
by LukeShu 7y ago
On a 6-month release-cycle, how much change do you want each release? (1.13 is scheduled to be released in August, following 1.12's release in February)
It's mostly not new number types, it's new number syntactic niceties.
As the guy who ends up maintaining the build tooling at work, I'm _very_ excited about a lot of the tooling changes:
- "Reproducible builds (independent of build path)" means 2 things to me: That customers building plugins for our product will no longer need to care about how our CI set GOPATH, and that I can drop hacks around the linker on macOS including timestamps (which would otherwise result in expensive Docker rebuilds)
- "Let 'go build' write many binaries" will let me adjust the build scripts to be faster, especially in mostly-no-op cases that my coworkers like to gripe about how slow it is.
I'm also excited about os.UserConfigDir.
- andy_ppp 7y agoI just want Golang to become a language suitable for my needs; it could be if they added generics (meh) or much better first class macros support (please don't tell me go generate it's not even close).