News for hackers. Stuff that matters.
[dead]
Re:Go 1.5.3 released to address security vulnerability by dang on Thursday January 14, 2016 @05:52PM (#10905404)
> As an aside, do you have any idea how pretentious you come across?

No personal attacks on HN, please. This comment would be fine without that last sentence.

Re:Go 1.5.3 released to address security vulnerability by eropple on Thursday January 14, 2016 @02:21AM (#10900050)
> You simply need to rebuild whatever binaries you run

"Stack", not "app". That includes, say, Docker. Or nsq. Which are packaged by the operating system (because, as noted in a reply to `tptacek, paying me to build out what they get from the operating system is generally not something a client is going to want to do). And which will not be updated as conscientiously as I can expect a core library on my system to be updated.

> As an aside, do you have any idea how pretentious you come across?

Pretension, frustration, whichever. My low opinion of Go aside, it's my job to deal with the details of my clients' stacks, make a coherent experience for their developers, and deal with the system-level security concerns they don't think about. If getting annoyed that Go and its community make my life suck a little bit more in ways it need not suck is pretension, I'm really gonna be okay with that. I mean, jeez, it's 2016. "Rebuild the entire world when a mouse farts" is fragile, dangerous garbage that puts the lie to the idea of "engineering" in this profession. We should be better than this. (And Go's first iteration, lovingly called Java 1.4, was. We're going backwards.)

Re:Go 1.5.3 released to address security vulnerability by elithrar on Wednesday January 13, 2016 @10:57PM (#10899519)
`go build -a` rebuilds all packages (i.e. those already cached under $GOPATH/pkg/ or /vendor).

Alternatively you can just rm -rf your `$GOPATH/pkg` directory.

Re:Go 1.5.3 released to address security vulnerability by nindalf on Wednesday January 13, 2016 @10:21PM (#10899418)
I can't understand why someone making a statement like that ("bloggable..") which is untrue can be upvoted while you're downvoted. Worse, he even bragged about being an excellent engineer who knows everything there is to know when he clearly doesn't in this case.