restruct VS go-japi

For me it's mux and my personal router restruct but since mux is not maintained anymore, maybe chi will be my goto for new projects that needs more stability in the api. Since restruct is a router based on structs, which I use for fast prototyping.

Not the best, but after using gorilla mux for routing for a while, I've decided to build my own https://github.com/altlimit/restruct

I've always just use gorilla mux and try to stay close to standard handlers as much as possible and code my request response process. As I've done this multiple times and actually been doing things over and over again I've developed my own router based on structs. Most of the time I develop something that's not going to be public api so I just want to easily build endpoints from struct method without defining new routes. I made https://github.com/altlimit/restruct for it. I also made it flexible so it can do a good amount of routing config. Then with same idea on authentication I made gauth. It's under the same org of that repository. Just to make my development for clients faster while sticking close to standards. I can't find myself using those frameworks that keeps introducing their own context somehow. I did use them before but somehow just doesn't feel right.

github.com/altlimit/restruct

Check out https://github.com/jarrettv/go-japi if you are building a JSON HTTP API. Also `go-don` is faster and supports other encoding formats.

go-japi and go-don are two small libraries that will do what you want.

The generic request and response wrappers seem interesting but they do tend to make the handler signature very verbose with little upside. For example: `type Handle[T any, O any] func(ctx context.Context, request T) (O, error)` would be really sweet. See go-japi for example.

Japi is a fork and simplification of another library. The upstream library go-don adopted fasthttp and our use case needed to stay on standard net/http.