A developer's blog on Go package management and vendoring, with older posts on PHP, jQuery, git subtree and minification.
HN commenters link it for Go package manager overviews and the git subtree install guide; they give no strong opinion of the blog itself.
I'm new to Go and I read some documents [1][2][3] on what 'vendoring' means but I still don't understand.
What problem does it solve? Why is it needed?
Is there an 'explain for a 5-year-old' version, or better yet, an 'explain for someone who is used to other packaging systems that may not be entirely elegant but work pretty okay most of the time, like Java's Maven or Node's npm'
[1] https://engineeredweb.com/blog/2015/go-1.5-vendor-handling/
[2] https://github.com/golang/go/wiki/PackageManagementTools
[3] https://docs.google.com/document/d/1rMoZ0rmpxw6dShalHnkuPtia6NkmB024MUa4T3SJeh8
The main differences are gzip doesn't strip out the documentation, and you don't need to decompress it. So in some cases the minified version would be smaller and a bit quicker. YMMV. I think it's trivial and you're right. Using gzip is easier and a bit more transparent.
Related article I found: http://engineeredweb.com/blog/why-minify-javascript/
When I wrote "Seeing How The Other Side Lives, A Package Manager Overview For Go Developers"[1] I noted CocoaPods. Was not aware of Molinillo though. Thanks for sharing.
[1] http://engineeredweb.com/blog/2015/pkg-mgr-overview/
`git subtree` seems like the perfect tool to complement `git submodule`.
Too bad it's not enabled by default: http://engineeredweb.com/blog/how-to-install-git-subtree/
http://engineeredweb.com/blog/09/12/preloading-images-jquery-and-javascript