I would also question the need for a "full-fledged" framework. The
motivation behind such frameworks is to make development (writing)
easier by either making some choices you otherwise have to make which
would require a deeper understanding of the problem and solution
domains or by deferring those
That is why a senior engineer creates a facade for the specific problem domain.
> On Jun 13, 2020, at 3:29 PM, 'Axel Wagner' via golang-nuts
> wrote:
>
>
> Maybe a dumb question but: Why would we *need* a standard framework?
>
> We're currently re-working this at my workplace and in the pro
Maybe a dumb question but: Why would we *need* a standard framework?
We're currently re-working this at my workplace and in the process, I've
looked at both go-kit and micro. Ultimately, at least as far as I can tell,
they don't seem to solve any of the problems I'm seeing, though. Both of
them te
Might not be the right place for this discussion but also useful to gauge
the experiences of the community. For the most part Go embodies a standard
library philosophy and most people are opposed to using any full fledged
framework. With Go now being a decade old, I feel as though with that
mat
