4 ms·
It is a fair enough point though. Even Go written by pros often does not fit together easily. Adjusting one library to fit with another is often a non-trivial
by jstewartmobile 9y ago
It is a fair enough point though. Even Go written by pros often does not fit together easily. Adjusting one library to fit with another is often a non-trivial task, and many package authors freely admit as much.
I must have links to at least five different gzip middlewares in my favorites, and I'm sure there are more than that...
- majewsky 9y ago> five different gzip middlewares At which point is it easier to put the app behind an nginx reverse proxy? Chances are that you have a reverse proxy anyway since one Go app is not nearly enough to saturate a server CPU.
- jstewartmobile 9y agoPoint being that something which could be easily slipped-in with a more dynamic language triggers a total re-wrap in Go, or punting to an outside system like your example. Not hating on it though. I like Go for network-y things. edit: And in your example, is it a clear win to centralize compression at the proxy?