> You gonna write backends for all that shit too in Go? The discussion is scoped to a single Go application. No one is proposing replacing NGINX with Go (or an

> You gonna write backends for all that shit too in Go? The discussion is scoped to a single Go application. No one is proposing replacing NGINX with Go (or anything else) for JVM apps. > won't have to go reading the source code for some crazy Go app program at 2am that also is a webserver for some reason? This is a rephrasing of the question I posed earlier--is it easier to manage configuration in Go source code or NGINX config files. > Separation of concerns, use it!! Concerns can be separated without being in distinct processes or implemented by distinct programmers or implemented in distinct programming languages.