|
Azazel posted:I use a combination of the standard net/http and gorilla/mux libraries myself, This. More often than not it's all I ever need, even for larger applications.
|
#
¿
Jul 17, 2014 14:48
|
|
|
|
| # ¿ Apr 29, 2024 06:43 |
|
|
Plorkyeran posted:Seems like the obvious solution to both the versioning problem and the unreliable third-party repo problem is to just fork all of the repos you depend on. Doesn't really let you have different versions of deps on different branches (without a fork per branch...), but if you control the repo you're pulling code from then you can just always have master pointing at the appropriate release. This is what we do at my shop. It's never posed a problem, and you always have the original repo if you need to pull any changes/fixes that made their way into the upstream.
|
|
#
¿
Oct 1, 2014 18:56
|
|
|
sarehu posted:I have a question for you Go people. Suppose you write a web application in Go. What do you do to get it running in actual production? Just throw the binary on your server and run it. Nginx is an option if you need any benefits from a reverse proxy. It doesn't get much easier.
|
|
#
¿
Mar 14, 2015 20:55
|
|
|
Coffee Mugshot posted:I don't know why people constantly claim Go is Google's baby. We have more external users than internal users by far and it's been an uphill battle to get people to use Go within Google. Python programmers maybe, but c++ and java programmers aren't that interested. It also gets basically zero attention at IO anymore. It's really just a project sponsored by Google more than anything.
|
|
#
¿
Oct 19, 2016 03:49
|
|