Echo: A fast HTTP router and micro framework in Go
I don't understand why people keep reinventing routers even though routing doesn't take much time anyways, especially in a compiled language like Go.<p>Most APIs seems to respond within 20 to 200ms. Even if you take 1ms to route stuff, what's the point in spending so much time in trying to optimize routing instead of SQL queries, cache layers or developer productivity with a nice ORM ? Trying to squeeze nanoseconds out seems pointless to me at the moment, especially since newcomers to Go end up seeing 20 different routers and might not know where to start.<p>I'm genuinely wondering.