howardjohn
Re:Stop picking my Go version for me
on Sunday March 29, 2026 @10:25AM (#47563424)
Thanks for the link! I could have sworn this was "fixed" and was surprised testing 1.26.1 showed the same (IMO bad) behavior! Didn't realize there was a revert. https://github.com/golang/go/issues/77923 looks like a hopeful path forward.
Re:Stop picking my Go version for me
on Saturday March 28, 2026 @11:22PM (#47560120)
I can admit that part was maybe a bit extreme :) fortunately in practice this would be a pretty rare situation IME due to how compatible Go is across versions.
(Blog author)
Re:Stop picking my Go version for me
on Saturday March 28, 2026 @11:18PM (#47560105)
I think Rust is slightly different in practice even if they behave the same technically. I'm not sure Rust lets you even set the MSRV to a specific patch which is the biggest annoyance with Go; if they do it's so uncommon I've at least never seen it. And I don't believe any Rust tooling encourages you to set the MSRV to <latest Rust version> like tools in the Go ecosystem do.
Re:LiteLLM Python package compromised by supply-chain attack
on Tuesday March 24, 2026 @10:02PM (#47512276)
agentgateway.dev is one I have been working on that is worth a look if you are using the proxy side of LiteLLM. It's open source part of the Linux foundation.
Re:Go 1.24's go tool is one of the best additions to the ecosystem in ...
on Friday January 31, 2025 @11:04AM (#42888870)
(Author of the blog here (the on in this thread, not the original submission))
Great question! I wasn't aware of the 1.24 optimization when I first wrote the post, but was interested to dig into this deeper. I updated the post: https://blog.howardjohn.info/posts/go-tools-command/#digging....
The tl;dr is...: 1. The new caching impacts the new `go tool` and the existing `go run`. 2. It has a massive benefit. 3. `go tool` is a bit faster than `go run` due to skipping some module resolution phases. 4. Caching is still (relatively) slow for large packages