Proposal trims http2 uplink buffer, Go's AI-era future debated

A proposal against x/net/http2 wants to shrink the uplink scratch buffer used by clientStream.writeRequestBody, arguing the current frameScratchBufferLen is heavier than it needs to be for sending request bodies. Over on r/golang, a thread picking apart the GopherCon 2025 "Go's Next Frontier" talk has people arguing about where the toolchain and language go in an LLM-shaped world, and a separate long post from a Laravel veteran of eight years explains why new projects now start in Go instead. For anyone who actually wants to look at the runtime rather than read about it, Gcscope showed up on the forum: a terminal UI for visualising Go GC behaviour, which is a nicer way to spend an afternoon than reading another build-times war story.