Re:So you want to expose Go on the Internet
by Can_Not on Friday December 23, 2016 @09:56AM
(#13244992)
You're free to not use nginx or Apache if you can validate that you are better off without them, but IMHO it sounds like a nightmare of "experimental homemade wheels" being muddled in with business logic.
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.