Next time someone says to me that language's popularity doesn't matter for it's utility, I'll remember how Go's socks library appears on the front page of HN, while my pull request the Haskell's socks library (which implements the most basic feature that author added to the top of TODO list himself) is sitting unmerged and uncommented now for almost a year.(1) (If I sound bitter it's because I am.)<p>Seriously though, such "boring" libraries that you just need in your toolbox are a great way to evaluate the health of the whole ecosystem.<p>[1][<a href="https://github.com/vincenthz/hs-socks/pull/24" rel="nofollow">https://github.com/vincenthz/hs-socks/pull/24</a>]
I will always say this was a complete hack to a specific time in history. Having SOCKS in your toolbelt of tricks is always handy and can make hard things surprisingly easy.<p>Last time was I needed to tunnel a request from my development environment into a production VPN to contact a service which had IP access restrictions.
If I only want the client side, does this add anything over <a href="https://godoc.org/golang.org/x/net/proxy" rel="nofollow">https://godoc.org/golang.org/x/net/proxy</a> ?