[abahmed]

Yes. You are right about that, but we think a bit differently. we think that would be a good chance for contributors that want to contribute to Go projects or frameworks, also tell that we are trying to build something better and surely we have a vision. For the benchmark, we already opened a PR (https://github.com/smallnest/go-web-framework-benchmark/pull...) after running it locally. Thanks For your feedback

[tcbasche]

"We haven't really done anything useful, but please someone come and make it better"

This is why we have so much crap on GitHub. OP has admitted this solves no real-world problems, and I would argue there is nothing wrong with net/http that it would require anyone to bother installing this stuff.

[abahmed]

Don't agree with you. We -gearbox community- are working on improving and adding more functionalities, not waiting as you said. Also, we welcome anyone wants to contribute and help us to make gearbox better. what meant by "solves no real-world problems" was that there are solutions (each one has its benchmarks) and what we are doing is trying to provide it with a better performance

[tcbasche]

But why market it as "gearbox is a web framework for building micro services written in Go".

If it's not production-ready, who are these micro services for?

It just seems not even close to polished enough to share it with the wider community. Someone may take this at face-value and try and use it for their own purposes, only to discover it's a purely academic pursuit with no actual merits other than 'oh we might be able to spuriously improve performance.'

I think other commenters have got it right in saying that processing requests is _not_ the bottleneck of most micro services, but interaction with a storage layer or network speed.

[abahmed]

Recently, we have mentioned that gearbox is still under development and not ready for production usage till we finish supporting all basic functionalities and have a benchmarks results (also for the current release). Thanks for your feedback