go vet proposal targets empty-struct map keys

A new vet proposal wants to flag `struct{}` and `*struct{}` used as map keys, on the grounds that pointer comparability makes the pattern tempting but rarely what the author meant. It is a small lint, but the kind that tends to surface real bugs once it lands. On the writing side, there is a piece arguing Java microservices can now match Go on a 2026 benchmark, which should generate the usual round of methodology arguments, and a Stackademic post on Docker conventions the author has stopped copying into every project. Over in the questions pile, someone is wrestling with how to mirror a nested C struct across the cgo boundary, which is one of those problems that never gets easier the second time.