Go isn't polymorphic enough as a language to achieve something akin to JEE, Rails, Django or Laravel, so these "go frameworks" will have hard time encapsulating the complexity of underlying libraries they might use. All the former use either an IoC container, or their own flavor of "module loading". This is absolutely not practical in Go.
Of course, dependency injection is possible, explicitly, but can hardly be generalized an efficient way, so the plumbing will always be explicit, because the underlying lib types will always leak.
So it's not so much that there is no value in frameworks in Go, it just hard to write actual web frameworks in that language that would be useful.
Of course, dependency injection is possible, explicitly, but can hardly be generalized an efficient way, so the plumbing will always be explicit, because the underlying lib types will always leak.
So it's not so much that there is no value in frameworks in Go, it just hard to write actual web frameworks in that language that would be useful.