@definitepotato

30 Followers
105 Following
65 Posts

#code slinger || #golang || #ziglang || grokking life || #tabletop games enthusiast || obsession with keebs and numbers



openpgp4fpr:6e34f5a9bdc72011436b8c29807ee32a2f083c6d

Githubhttps://github.com/definitepotato
Keyoxidehttps://keyoxide.org/hkp/6e34f5a9bdc72011436b8c29807ee32a2f083c6d
Bloghttps://www.definitepotato.dev
I like to learn by teaching. It reveals the gaps in my knowledge and tests my understanding. Started writing a book for the #zig community and spent months writing the code, making sure each block of code builds and the language makes sense. In the midst of writing content for the second-half of the book, I paused. I started to ask myself about the meaning of it all in a post-AI world. I’m beginning to question the value of it to the community when the problem it solves is a prompt or two away.

One of the most practical and useful books of my career has been the Thorsten Ball series of writing an interpret/compiler in #golang. I wanted to give to the #zig community so I've written a guide/book at https://www.definitepotato.dev/books/ called From Interpreter To Compiler in Zig.

It's essentially Thorsten Ball's structure but in Zig. I plan to maintain it as the zig compiler develops and I learn to do better.

Books

Online books by definitepotato

definitepotato

" What should we do with CLs generated by #AI "?

A discussion on `golang-dev` begins when a #Golang dev noticed Claude as a co-author on a contribution. Responses from people other #Go devs include legal issues, licensing issues and extensive thoughts. Interesting post to read and follow:

https://groups.google.com/g/golang-dev/c/4Li4Ovd_ehE/m/UU87HnL5DgAJ?pli=1

What should we do with CLs generated by AI?

Two new packages management features just added to #ziglang

- Fetched packages are now stored locally in the zig-pkg directory
- The zig build command gets a fork flag to override the entire dependency tree of a project given a path to the source

Read more: https://ziglang.org/devlog/2026/#2026-02-06

Devlog ⚡ Zig Programming Language

#golang 1.26 is released https://go.dev/blog/go1.26

- new built-in function
- gc performance improvements
- go fix command has been rewritten
- experimental simd operations added
- experimental temporaries secret eraser added
- experimental goroutine leak detection added

Go 1.26 is released - The Go Programming Language

Go 1.26 adds a new garbage collector, cgo overhead reduction, experimental simd/archsimd package, experimental runtime/secret package, and more.

AI could force popular #FOSS projects to close PR submissions from the public.

Results from the latest #golang developer survey conducted in September2025.

https://go.dev/blog/survey2025

Results from the 2025 Go Developer Survey - The Go Programming Language

The 2025 Go Developer Survey results, focused on developer sentiment towards Go, use cases, challenges, and developer environments.

The juice has arrived at https://codeberg.org/ziglang/zig/pulls/30644

I've written a quick summary of what this merge means for #zig in 0.16.0 https://www.definitepotato.dev/posts/20260120-zig-juicy-merged/

std: delete `os.environ`, `os.argv`, add new parameter to `main`, move process API to `std.Io`

Happy New Year! 🥳 I'm celebrating the arrival of 2026 in my favorite way: breaking "Hello, World!" again! Mainly the goal was to delete the "environ" global variable as well as the "argv" global variable because they are footguns. However, in doing so, I ended up needing to integrate process API...

Codeberg.org

An interactive tour of what's coming to #golang 1.26 next month

https://antonz.org/go-1-26/

Go 1.26 interactive tour

New with expressions, type-safe error checking, and faster everything.

Not the #esp32c3 I was looking for https://sigmacoffee.co.uk/products/chestnut-c3-esp
Though maybe it does Java (sorry, so sorry 🤦‍♂️)
Timemore Chestnut C3 ESP Pro Manual Coffee Grinder