Probably mostly off-topic, but every time I see the words “Go” and
“framework” together in a sentence, I can't help but chuckle. Go is,
idiomatically, a very anti-framework and pro-library language. And
I think that that's a good thing. The closest thing idiomatic Go has to
frameworks are the stdlib's “interface packages” like package image or
package database/sql/driver, which are amazing because they make it
easier to create an actual ecosystem instead of a network of
incompatible frameworks. Anyone who wants to create a “framework” for
go should instead learn from those packages and try to define a set of
interfaces which work together to achieve a goal.