Sam
borkent.bsky.social
Sam
@borkent.bsky.social
github.com/samborkent
As a Go lover, I find it interesting that the language chose to have default zero values, which I've learned to appreciate, and nil at the same time.

Go enjoyer paradox: liking the fact that there will never be a Go v2, and disliking the fact that there will never be a Go v2 with nil-safety.
December 19, 2025 at 9:37 PM
I know multiple companies that (mis)use Kafka as their primary database.
December 17, 2025 at 7:31 AM
UUID v7 is preferred
November 26, 2025 at 10:15 PM
Some applications rely on memory layout of structs (e.g. fast parsing libraries). It would also break cgo. And this will not always be faster due to caching, see skoredin.pro/blog/golang/....
You can simply use the fieldalignment tool and do it manually. pkg.go.dev/golang.org/x...
CPU Cache-Friendly Data Structures in Go: 10x Speed with Same Algorithm
False sharing killed our performance. Data-oriented design saved it. Learn cache lines and NUMA.
skoredin.pro
November 26, 2025 at 7:14 AM
Just do `var[:]` to get a slice of all elems in array.
November 24, 2025 at 7:33 AM
As Go dev I mostly use bsky.app/profile/did:...
November 4, 2025 at 7:06 AM
Go explanation: Imagine you have a const interface (doesn't exist in Go) and then try to force it into a var using unsafe so you can write to it.
November 3, 2025 at 7:39 AM
Good question. The Google package is the defacto standard and IMO can almost be considered a "standard" library. github.com/google/uuid

Same question could be asked for github.com/google/go-cmp why it was never adopted in std lib.
October 25, 2025 at 10:01 AM
The std lib already has these cases. For example, `crypto/rand` and `math/rand/v2` which I often use together.
October 10, 2025 at 8:44 AM
Agreed, maybe they should allow defining import alias in go.mod, so it's forced project wide.
October 10, 2025 at 8:43 AM
Because error checking is slower. You can still do the same thing by giving your custom iteration implementation an Err() method and checking that after the iteration loop. You could even let it return an error channel to handle errors for each value.
October 9, 2025 at 10:39 PM
I've only worked serverless with AWS Lambda and Knative, and both work great with Go, so I can't give much advice here.

My favourite way to deploy Go backend is through fly.io. They have decent Go documentation and a fair free tier if you stay under a certain usage limit.
September 24, 2025 at 4:48 PM
Right. I haven't used Flutter, let alone it's wasm target. But I do know the wasm implementation of Flutter is a lot more mature than Go's, so I have considered in the past if it would be worth it to learn Flutter to give it a go.
September 24, 2025 at 4:41 PM
Cool! How do you like this stack?

Whick platforms do you target? Have you tried wasm?
September 24, 2025 at 4:20 PM
For slog I inline the actual error in the message: slog.Error("some error: "+err.Error()).
September 24, 2025 at 4:17 PM
Technical Papers – Cytomic
cytomic.com
September 7, 2025 at 8:50 PM
Doing the lords work. How did you start contributing to the Go project?
August 31, 2025 at 8:32 AM
The article concludes that they will not make changes to error handling syntax?

How do you conclude Go might get different syntax?
August 31, 2025 at 8:31 AM
Not a good take. Go can definitely make you a better engineer. It's selling points are long term language stability, and quick development, with powerful concurrency model.
August 21, 2025 at 7:00 AM
Right, cool. Thanks for the explanation! Nice project.
August 19, 2025 at 5:59 AM
What does this offer that Context7 does not?
August 18, 2025 at 11:23 AM
Nice! The more full-stack options in Go the merrier.
August 6, 2025 at 9:16 PM
Go is one of the most readable languages. The error handling might be verbose for some, but it's definitely very readable.
August 6, 2025 at 9:12 PM