On: Practical Go: Real-world advice for writing maintainable Go programs

[akerl_]

The issue w/ calling it "config" is that you end up with the confusing scenario where "config" is the object and "Config" is the type, differing only in casing.

[pcwalton → akerl_]

Why is that confusing? Local variables are, idiomatically, never capitalized in Go, so the distinction is obvious at a glance.

[akerl_ → pcwalton]

Sorry. To clarify: it's not that I'm confused by the distinction between capitalized vs uncapitalized, it's that visually, "config" and "Config" look quite similar at a glance, whereas "c" and "Config" are clearly visually distinct.

[rat9988 → pcwalton]

As are unexported objects.

[ben0x539 → rat9988]

Yeah, getting to idiomatically capitalize names has been pressure to move them to their own package in the past, which feels awkward.

[bpicolo → akerl_]

This is a fairly go-specific issue due to its unexported vs exported convention. Many languages solve this through case conventions