4 ms·
> With increasing amounts of SW development moving to low-cost countries, this sort of attitude may well eventually destroy the availability of the 'free' softw
by kuschku 11y ago
> With increasing amounts of SW development moving to low-cost countries, this sort of attitude may well eventually destroy the availability of the 'free' software that these manufacturers rely on (besides hurting the GPL + homebrew firmware communities).
Even in developed countries, a lot of projects that historically chose BSD or MIT ("why should we choose GPL? Companies will contribute back anyway") are starting to change their mind because more and more companies just take publicly available code and sell it, never contributing back. Just think about Google (which uses Apache code, but doesn’t contribute back) or VMware (which openly violates the GPL).
As long as humans are greedy, we’ll have to find a technical solution to protect against such immoral people or organizations.
- viraptor 11y agoI'm not sure why you put "Google (which uses Apache code, but doesn’t contribute back)" and "VMware (which openly violates the GPL)" in the same sentence. One is legal, the other one isn't. You're not forced to contribute to anything, GPL or not. But it's worth remembering that Google's involvement goes further than just extra commits. For example - if Google uses something, they'll likely do a better security testing of the product than many other companies. Their security reports always go back to other projects.
- kuschku 11y ago> I'm not sure why you put "Google (which uses Apache code, but doesn’t contribute back)" and "VMware (which openly violates the GPL)" in the same sentence. One is legal, the other one isn't. You're not forced to contribute to anything, GPL or not. Simple: While legally there’s a difference between Apache and GPL, from a purely ethical standpoint, there isn’t really – you took something that belonged to the public, you contribute back to the public.
- cyphar 11y ago> > I'm not sure why you put "Google (which uses Apache code, but doesn’t contribute back)" and "VMware (which openly violates the GPL)" in the same sentence. One is legal, the other one isn't. You're not forced to contribute to anything, GPL or not. > Simple: While legally there’s a difference between Apache and GPL, from a purely ethical standpoint, there isn’t really – you took something that belonged to the public, you contribute back to the public. Which leads to the question "why not use the GPL for everything?". To be honest, I actually fall into the camp of "we should be pushing for the GPL for most non-trivial software".
- sangnoir 11y ago> Google (which uses Apache code, but doesn’t contribute back I disagree. Outside of Raleigh, I think Google is currently one of the biggest champions of 'giving back' in letter and spirit (code contributions and research papers). Would you mind expanding on how Google doesn't give back?
- kuschku 11y agoHave you seen what happened with the Android Open Source Project recently? Google took the code and closed almost all of it. They took, but don’t give back: The Email Client, the Launcher, the Dialer, the Calendar, the Contacts app – all of that is now closed source. You can’t do anything on Open Source Android anymore.