I’ve referenced this post many times to co-workers. It’s a great summary of different routing approaches and libraries. In my open source project I do not use a routing library at all, and I use something similar to what the author describes as “Regex table” (except I just do if-then-else), which is sometimes annoying, but also dead simple.
An option since that article came out is Alex Edwards’s Flow router: https://pkg.go.dev/github.com/alexedwards/flow
My immediate thought was “Doesn’t Edwards also have an article about HTTP routing in Go?” He does, and you submitted it here about a year ago. I resubmitted it now so that people can compare.