Don't name packages common nouns

As an aside, I like the site author's Atoms/Fragments/Articles hierarchy for content on their website -- both in intent and the names themselves. I've been trying to come up with similar thresholds for my own work. Useful idea!

So, instead of using an import alias for the odd case where you want to name a variable the same name as the package, you will force everyone using the package to have "the java stutter": ratelimiter.Limiter, or ratelimiter.RateLimiter.

Nope. No thanks. I'll stick with aliases and keeping my variables names short depending on their "proximity of use"[1].

[1]: https://go.dev/talks/2014/names.slide#4