To view parent comment, click here.
To read all comments associated with this story, please click here.
True, and not so true. Keeping the code open never prevented people from making a bussiness out of GPL, several companies do 'sell' GPL-code. In fact, they sell the services to maintain the code and having it open ensure the client to 1/ control what's is inside the code 2/ switch maintainer if original publisher/maintainer disapear (bloody raging captalism)
Having GPL code is not *THE* problem all along, provided your product *CAN* be as open. No, *THE* problem is where the product have to *HIDE* something from eyes, like secret cryptography or receipe, drm, whatever. Thus using GPL should in some extend obligate you to open your code in GPL as well. On the other hand you could always give the finger salute to RMS and protect your 'privacy' bits inside a dll or similar. However RMS is a pitbull when it comes to defend his dogma...
I do (and prefer) using/releasing in zlib/png licence, which is pretty close to public domain ou MIT, to sum up : do whatever you want, close the code, open it, burn your guitar, listen to meatloaf, ... You ethic as a coder shouldn't be driven by someone's paranoid beliefs in "openess" but by providing the *BEST* solution to a problem, period. So do people's ethic shouldn't be dictated by religious means or similar tubes, common sense and citizenship should be enough. But that's another story...
Kochise




Member since:
2005-07-13
I guess it depends on which you think is more important: the freedom of an individual to make use of your code as he or she chooses, or the freedom for society in general to access the source code of the software it uses.
Personally I'm not sure either are a right, but they both strike me as types of freedom (both of which are worth promoting).