Ask HN: What Do Go HTTP routing libraries get wrong? And how can we fix it?

Hey HN,

I'm working on developing a new HTTP router for Go, and I'm curious to hear from the community about what features you'd like to see added. Specifically, I'm interested in:

1. Common Pain Points: What issues have you encountered with existing Go HTTP routers? Are there particular features or functionalities that you find lacking or problematic?

2. Desired Features: What new features or improvements would you like to see in a Go HTTP router? This could be anything from better performance, more flexible routing patterns, easier middleware integration, etc.

3. Comparisons with Other Libraries: If you've used routers in other programming languages or frameworks, what features or design choices do you think should be adopted by Go routers?

Your feedback will be invaluable in helping shape a router that addresses real-world needs and improves upon the current offerings. Thanks in advance for your insights!

Best Regards, Sam!