Python's Stamina for Go: Bringing Ergonomic Resilience to Gophers

If you've ever worked in the Python ecosystem, you've likely encountered tenacity or its opinionated wrapper, stamina . They make retrying transient failures feel like magic: a single decorator, sensible production defaults (exponential backoff + jitter), and built-in observability. The Go ecosystem has powerful tools, but they often require a lot of boilerplate, use reflection, or lack the "Correct by Default" philosophy that makes stamina so great. That's why I built Resile . It’s a love letter to Python's ergonomics, written in idiomatic, type-safe Go 1.18+. The Ergonomic Gap In Python, retrying an API call with stamina looks like this: import stamina @stamina.retry ( on = httpx . HTTPError , attempts = 3 ) def get_data (): return httpx . get ( " https://api.example.com " ). json () Before Go 1.18, achieving this level of simplicity was nearly impossible. You either had to write verbose for loops or use libraries that relied on interface{} and reflection—which meant losing type safe