Re:Google Just Did a Pad-Left on Go (For App Engine)
by erlichmen on Thursday March 24, 2016 @11:23AM
(#11353510)
My Google Product (which is fully supported) broke because of a Google commit
Re:Google Just Did a Pad-Left on Go (For App Engine)
by jerf on Thursday March 24, 2016 @12:34PM
(#11354220)
I see and acknowledge that. That is not a "pad-left" issue. That is "a commit broke my code". If that set off a pad-left sized reaction every time it happened HN would be nothing but "commits that broke code" on the front page every day.
I assume you weren't vendoring before... are you vendoring now?
Re:Google Just Did a Pad-Left on Go (For App Engine)
by erlichmen on Thursday March 24, 2016 @12:45PM
(#11354319)
For the sake of the argument lets say I vendor my code (notice that this is 1.4.2 golang and most vendoring tools were formed around 1.5), This doesn't help a guy that tries today to start a new project on Google AppEngine/Go using Google code. Major functionality is broken in the sense that he can't compile his code. Google Samples (and from official documentation) is broken. How vending helps in that case?
Plus the Go community's quasi-official position as of 1.4.2 was still that you should vendor your dependencies, and "you should vendor your code" is the official position now. If your code broke because of a remote commit on the internet, that's your build system's problem, not the internet's.