As I said, if proprietary software incorporates permissive software, said permissive software is still open source. It does not amount to fascism or any of the non-sense above.
Originally Posted by brosis
I mean, there are several examples of this. Matlab uses LAPACK for example. LAPACK is still actively maintained and open source.
Can you provide an example? You can't patent an algorithm that has already been publicly disclosed ... this a bunch of hot air. However, if an open source developer (regardless of license) implement a patented algorithm without the consent of the patent owner, even this developer would be in a great deal trouble.
Yes, this is true. They like to produce closed source anti-freedom software, that incorporates A LOT of permissive software. They like it even better, if they can patent this software or otherwise make it exclusive to them. GPL does not deal with slavers, that's the point. But otherwise, no one is limited or dictated of the ways to monetize the software in GPL.
I think software patents are annoying as much as anyone else, but that's just how it is. Use Google Patents to check first.
Furthermore, much of the software used in proprietary software is non-trivial. It would be impractical for the company to, "make it their own," unless some secrets were at stake. Besides, what do they gain by making open source software "their own?" From what I can tell, companies would rather pull updates from the open source project and submit their changes back. This is just practicality. Who would want to spend time merging private changes back into every update?
And the EULA of the proprietary software does not affect the permissive software used in the proprietary software. The permissive software remains open source and unencumbered.
Also the "private modifications" you talk about are garbage, because your very own EULA imposes much much more restrictions than GPL does. And if you don't want to opensource your "private work", keep it to yourself, lock it up, let it rot. You know, its a general rule of information, information is multiplied via reusal, so go ahead, keep it private.
If you're worried about a corporation profiting off your work and this really bothers you, then maybe the GPL is right for you. Unlike you, I'm not a zealot.
And if you want to make use of someone's "sweat", but refuse to reveal your "modifications", then you are better off with BSD license. Nothing wrong with that, just more restrictive software taking money away from uninformed customers and polluting the climate with own useless noise.
However, more often than not, proprietary software is non-trivial (otherwise, who would buy it?) and just makes use of simple algorithms (e.g. like SVD). I wouldn't consider using, for example, SVD, worthy of releasing the entire work as open source GPL software. Would you?
If you want your software to be widely adopted by the community (corporate, open source, government, etc...), a permissive license is a good way to go. Otherwise, it will likely rot in the open like some of the FSF software now (because many cannot use it due to its restrictions).