4 ms·
I realize that much of the Go community is hesitant about the sort of third-party code that intentionally constraints the problem-space by restricting choice an
by niftich 9y ago
I realize that much of the Go community is hesitant about the sort of third-party code that intentionally constraints the problem-space by restricting choice and then calls your code at a few well-defined points; preferring to call out to libraries instead (vs. the other way around); but what solutions, if any, are widely utilized to avoid the above situation?
- tyingq 9y agoGuessing most people that care about this would have some sort of "minimum http header/feature" test that runs each build.
- omginternets 9y agoI quite like http://echo.labstack.com http://echo.labstack.com I quite like it because you can access the net/http constructs (ResponseWriter, Request, etc) if you really need them, but in most cases it removes a lot of boilerplate.