On Mon, 2017-07-10 at 11:40 -0500, Adam Miller wrote: > The main motivation for bundling as of late is golang[0], it's > extremely common out in the community for software to pull in > "Vendored" libraries even if they are exact copies of remote > upstreams > (this is common with tools like godep[1]) because golang is > statically > compiled by default (you can dynamically link with gcc-go and I > *think* recent releases of cgo but I've yet to find a golang project > that officially uses or endorses it's use). It's also extremely > painful to unbundle these as some more popular software written in > golang such as docker[2], kubernetes[3], and openshift[4] have > upwards > of 100 bundled libs (over 1000 for OpenShift). On top of these problems I have also observed a trend away from having releases and versions at all. Lots of golang programs just depend on git commit hashes of libraries that don't make releases. I've also observed this problem in some JavaScript libraries.
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
