I've done this many times as a lazy way to split up a large chunk of work. It always felt hacky, like there should be a better way, but it's interesting to see I'm not alone!

staticcheck.dev does a good job with its "unused" analysis, but it only looks at unexported names, as it's a generic static analysis.

pkg.go.dev/golang.org/x... instead takes package entrypoints, and points out unreachable funcs, but no fields. But it can do exported funcs fairly well.

I'm afraid to ask what they smell like.

GerritHub exists, but it's slow and rough around the edges. And it provides no out of the box requirements for large teams like CI integrations or merge queues.

I am hoping the plan is to build a code hosting and review system - I love Gerrit with its patch versioning and stacking, but it's also horrible UX.

Plus, it having no GitHub-like service pairs poorly with how difficult it is to self-host.

The desktop electron app indeed resolves this; it has a sidebar to switch workspaces, much like Discord.

You can "discover" and log into your worskpaces by email too, in case you lose track of them.

I'm not working on go-yaml, I haven't looked into what they are doing with v4 yet.

Video is up now - my take on how map is implemented in Go, and what changed from Go 1.23 to 1.24 and 1.25.

youtu.be/M05t7Q6LbFs

Maybe @qmuntal.bsky.social can chime in - this is well beyond me 😅