Incidentally I saw the Wes McKinney podcast who said that Go was the perfect language now because of the fast compile-run cycle with strong types and built in multi thread safety was perfect for Coding Agents. Gave me a whole new interest. https://www.youtube.com/watch?v=1VfzDXeQRhU
Using go fix to modernize Go code
71–80 of 97 posts
Re: Using go fix to modernize Go code
#72Earlier quoted context omitted.
This is one area where reinforcement learning can help. The way you should think of RL (both RLVR and RLHF) is the "elicitation hypothesis[1]." In pretraining, models learn their capabilities by consuming large amounts of web text. Those capabilities include producing both low and high quality outputs (as both low and high quality outputs are present in their pretraining corpora). In post training, RL doesn't teach t…
I believe you absolutely could... as the model owner. The question is whether Go project owners can convince all the model trainers to invest in RL to fix their models and the follow up question is whether the single maintainer of some critical but obscure open source project could also convince the model trainers to commit to RL when they realize the model is horribly mistrained. In Stackoverflow data is trivial to…
I think this can be fixed more generally by biasing towards newer data in model outputs and putting more weight on authoritative sources rather than treating all data the same. So no one needs to go in and specifically single out Go code but will instead look at new examples which use features like generics from sources like Google who would follow best/better practices than the rest of the codebase.
Re: Using go fix to modernize Go code
#73Earlier quoted context omitted.
Good use case for Elixir. Apparently it performs best across all programming languages with LLM completions and its concurrency model is ideal too. https://autocodebench.github.io/
This is the exact opposite of my experience. Claude 4.6 has been excellent with Go, and truly incompetent with Elixir, to the point where I would have serious concerns about choosing Elixir for a new project.
We live in different realities.
Opus and Sonnett practically writes the same idiomatic elixir (phoenix, mind you) code that I would have written myself, with few edits.
It's scary good.
Re: Using go fix to modernize Go code
#74Incidentally I saw the Wes McKinney podcast who said that Go was the perfect language now because of the fast compile-run cycle with strong types and built in multi thread safety was perfect for Coding Agents. Gave me a whole new interest. https://www.youtube.com/watch?v=1VfzDXeQRhU
[dead]
Re: Using go fix to modernize Go code
#75Earlier quoted context omitted.
You should be using rust... mm kay :\
Doing concurrency in Rust was more complex (though not overly so) than doing it in Golang was, but the fact that the compiler will outright not let me pass mutable refs to each thread does make me feel more comfortable about doing so at all. Meanwhile I copy-pasted a Python async TaskGroup example from the docs and still found that, despite using a TaskGroup which is specifically designed to await every task and only…
The person I was replying to sounded exactly like the Rust zealots roving the internet trying to convince people to change.
Re: Using go fix to modernize Go code
#76[flagged]
Re: Using go fix to modernize Go code
#77[flagged]
Re: Using go fix to modernize Go code
#78Not related with go: I recently tried to learn Python beyond the classical example code from the web. After discovering that there are more or less 4 different ways to do a thing with no clear guide what best practice is. I come from C and there one is happy if there is ONE way to do a thing :). Is Go at this stage? Im Intrested in learning Go but not to a point where i need a LLM to determin if my code follows best practice.
Re: Using go fix to modernize Go code
#79Earlier quoted context omitted.
> a subtle data race and a rare deadlock That's a langage problem that humans face as well, which golang could stop having (see C++'s Thread Safety annotations).
You should be using rust... mm kay :\
So you are trying to explain concurrency to the folks who implemented CSP in both Plan9 and Go. Interesting. I should return "cspbook.pdf" back.