Just Use Go

I like go, but a lot of little things stop me from loving it.

Like, enums. I get a lot out of the box when I use an enum in Java or Kotlin. Converting to/from a String is trivial. Type safety ... exists.

I can do that in Go, but I have to hack it in, for every single enum type I want to represent. Enums are not a thing in the language, which means its easier to keep the language in your brain all at once, but at the expense of making it harder to keep the software I'm writing in my head. Is this "enum" the same as that "enum"? I have to go read the code to figure it out.

But Go is excellent at a lot of things. Compile times, static binaries, resources compiled right into that binary, execution speed ... there is a lot to love.

Go, similar to Rust, has a horrible ecosystem, IMHO. I want to like it, but they already broke backwards compatibility with older systems (try to get the Go compiler running on a slightly older OS X, f.ex.), and for a compiler that's a no-go to me.

A dig at Django's ORM seems hilarious. I wonder how many SQL injection vulnerabilities are written daily by Go devs.

archived: https://nonogra.ph/just-fucking-use-go-05-08-2026

I wrote about this here [1]

The big idea with LLMs is consistent references in the training corpus produced cheddar output by the language model during inference.

Go is an amazing language for language models because it's actually quite boring predictable while packing a lot of powerful distractions with a world class tool chain supported by Google and strong std library as well.

As a programmer I actually hated writing Go... and wanted to write Rust; but using coding agents makes me appreciate writing Go more.

I can get consistent results out while having concurrency cross compilation and predictability.

https://jry.io/writing/ai-makes-golang-one-of-the-best-langu...