… by adding a check to builds that anyone, using the source code, can easily patch out?
FOSS never came with any guarantee of “builds must arrive in format most convenient for users.” That’s not in the license. Also not in the license, “FOSS companies can’t charge money for their builds.” Also not in the license, “FOSS companies must provide builds at all.”
If anything, it’s quite a bit of entitlement that “FOSS companies must provide free code, and free builds, forever, or they are evil.” Especially when they are getting VC money to presumably add features that otherwise would not exist and would have no code available at all.
Yes by adding friction to any existing user so they have to fuck with it every single time they update instead of just downloading a blob.
Now Go being easy to get builds running makes it less painful, but still, the entire reason it is in codebase is to add friction.
> If anything, it’s quite a bit of entitlement that “FOSS companies must provide free code, and free builds, forever, or they are evil.” Especially when they are getting VC money to presumably add features that otherwise would not exist and would have no code available at all.
I don't consider "OSS license with CLA forcing code rights assignment" to be FOSS. It being closed source would be better for everyone (but them) because less people would get baited into bait and switch and maybe support less insidiously managed projects.
FOSS never came with any guarantee of “builds must arrive in format most convenient for users.” That’s not in the license. Also not in the license, “FOSS companies can’t charge money for their builds.” Also not in the license, “FOSS companies must provide builds at all.”
If anything, it’s quite a bit of entitlement that “FOSS companies must provide free code, and free builds, forever, or they are evil.” Especially when they are getting VC money to presumably add features that otherwise would not exist and would have no code available at all.