https://github.com/golang/proposal/blob/master/design/2775-b...
Is it? I've never heard of this or seen this.
Really? How exactly this will decrease the quality of open source libraries?
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).
Look at the C/C++ ecosystem which has many commercial libraries, as well as open source ones. Boost is an excellent, source-code included library. No harm is helping commercial vendors of libraries making their, say, C++ quantitive finance library available to Go devs too.
The whole rationale given in the proposal [1] is that some users have worked with vendors who do not want to share their source code, since they've purchased some sort of library product. In my opinion, that's likely more harmful than beneficial for software as a whole.
[1] https://github.com/golang/proposal/blob/master/design/2775-b...
I'm not sure why that's "likely more harmful". If you're purchasing enterprise software or specialized hardware that comes with libraries that interact with them I can understand companies not wanting to simply hand over the source code to such things (this is how it's done with many existing products outside of the GO ecosystem).
There is nothing wrong with giving people the option to deploy either way and it will help the GO ecosystem gain more enterprise like users.
A decade or three ago, it was common for all software not to come with source code. If you bought some server software, the client library was closed-source as a rule, if it even existed, regardless of how enterprise or non-enterprise it was. Now it's not uncommon to see even closed-source services have client libraries on GitHub because that's where they're expected and that's how people expect to publish client libraries. That change seems to have been good for the industry and good for the world.
The enterprise users will come along eventually. They always have; you can find articles as recently as a decade ago debating whether your company should allow the use of open source software internally, or have a blanket rule against it. The second option is now inconceivable for almost all companies, because you put yourself at such a competitive disadvantage. All Go needs to do is deliver a technically attractive product, and people will figure out how to be comfortable using it.
But they do so, by delivering it encrypted and decrypting it on the fly when it gets used.
Or they hide it on a server that their customers never get to see, besides an incomprehensible junk of minified and encrypted JavaScript.
Which companies are doing successful business selling software for embedded, desktop and mobile platforms with source code available?
A number of software-as-a-service companies are making extremely successful businesses with completely proprietary servers and open libraries. Amazon AWS and Slack both come to mind without thinking very hard, but there are a lot of others.
If you want to reject software-as-a-service, there are a good number of companies selling proprietary (or at most "open core") desktop/server applications with open-source client libraries. VMware, a bunch of NoSQL companies, a couple of network monitoring tools, etc. also come to mind. Those sorts of companies would have given you a closed-source C library 10-30 years ago.
And, of course, there are people who sell hardware (graphics cards, network cards, RAIDs, etc.) who would have released proprietary tools and drivers in the past and are now releasing both as open-source because that's a competitive advantage because their stuff works better.
Also the commercial games that are sold with it surely don't come with source code.
This PR is also not required for executables without source, which Go has supported forever, just for libraries without source.
Those vendors will just keep using tools whose vendors are more understanding of businesses needs, like C and C++.
FWIW: This doesn't enable you to do anything you couldn't do before; it just makes it less annoying.
Maybe it's just fanciful and impractical, but I'd sort of hoped this would be the kind of decision that Go could take a stand against, in favor of incentivizing openness.