Re:Include Go binary only package
by dchest on Friday April 29, 2016 @03:54AM
(#11594339)
It's not compiler's job to shape community or enforce ethical values (unless it's GCC, haha). If people don't want to share binaries, they are free to share sources.
[ Parent
| on HN ]
From a utilitarian perspective this will cause more harm than good to golang. Enabling users to ship binary blobs instead of open source openly audible code will decrease the over all quality of golang libs. Its the job of those who write the compiler to move the project in a direction which is best for golang, and this direction arguably is not good for golang.
will decrease the over all quality of golang libs
Really? How exactly this will decrease the quality of open source libraries?
I think OPs point is that commercial vendors will now stop providing the source code, which deprecates the overall quality (I don't like working with code I don't have the source code to. Once you find a bug, this all blows up on you).
It think it is a big win that proprietary software needs to ship source code with them in order to sell the library. Just because there is source code doesn't mean, it is open source or free software. It can still have the same licenses (not share the source/bin, etc) but source code that is visible (even proprietary) is better then a binary.
After all, not all libraries are OS and those that aren't would suffer from that change (although marketing guys would probably argue differently).
Exactly, which is why it's great for community! This means that open source packages will be more valuable than commercial binary blobs due to the ability to audit source code.
Theoretically, yes, but commercial libraries will always be there – no matter what language they're written in. So we can either make the best out of our situation and have commercial libraries with source code access or have it like every other language out there.
Re:Include Go binary only package
by youjiuzhifeng on Friday April 29, 2016 @06:49AM
(#11594857)
From Go 1.5 version start, go compiler can compile packages as a shared library. Although this feature is limited, It is really welcome to share a binary package.
http://blog.ralch.com/tutorial/golang-sharing-libraries/
Re:Include Go binary only package
by matthewmacleod on Friday April 29, 2016 @05:06AM
(#11594537)
You are right, of course – but like all things, the decisions taken by the development environment can shape the community!