News for hackers. Stuff that matters.
Re:Include Go binary only package by kristianp on Friday April 29, 2016 @12:37AM (#11593788)
It does seem bad for open sourceness, there's a rationale section in the proposal for this feature:

https://github.com/golang/proposal/blob/master/design/2775-b...

Re:Include Go binary only package by lucaspiller on Friday April 29, 2016 @05:53AM (#11594678)
"Various users have reported working with companies that want to provide them with binary but not source forms of purchased packages. We want to define an explicit way to do that instead of fielding bug reports each time the go command gets smarter about detecting source-vs-binary mismatches."
Re:Include Go binary only package by zimbatm on Friday April 29, 2016 @10:46AM (#11596039)
The answer could also be to ship an executable and then use IPC instead.
Re:Include Go binary only package by Matthias247 on Friday April 29, 2016 @02:55PM (#11597911)
That has completely different performance characteristics. And for sane usage you need then some code again in the main program that encapsulates away the IPC basics. And it won't work for all use cases, e.g. moving parts of the GUI into a different process will most likely not work.
Re:Include Go binary only package by hobarrera on Friday April 29, 2016 @02:46PM (#11597848)
Under what circumstances is this necessary? I can't think of any valid use-case for this odd feature.
Re:Include Go binary only package by hobarrera on Friday April 29, 2016 @02:46PM (#11597856)
> It is common in C for a code author to provide a C header file and the compiled form of a library but not the complete source code. The go command has never supported this officially.

Is it? I've never heard of this or seen this.