Slashdot Mirror
Viral GPL Misconceptions Elegantly Explained
Scot W. Stevenson writes "Our favorite paralegal Pamela Jones of Groklaw has put together a short FUD-killer on the General Public License that explains why you can't lose your proprietary code if you inadvertently incorporate GPL code. This is not the only text of its kind, but it is so well explained that you might want to bookmark the page for future reference."
New open letter idea: explain how you CAN lose your free code even if you don't incorporate any SCO code into it, as long as SCO keeps saying you have.
The real Ralph Yarro posts as Anonymous Coward. Anyone else is an impostor.
Did you read the article?
Is this a trick question or something? How was I going to get an obvious troll high enough for people to read if I actually took the time to read the article?
I mean, duh.
Yeah, I could not resist the pun, but apparently the moderators could...
I've only been programming for about 15 years, so maybe it's just my lack of experience talking here, but... never have I had it happen where a library simply links itself into my program of its own volition. If you know of a way to make this happen, I'd love to hear it, because it would save me loads of time grepping through assorted header files to figure out a library interface, reading documentation, etc. It would be a dream come true.
Incidentally, in every (L)GPL'd library I've ever used, the licensing terms are spelled out clearly right there at the top of said header files. You'd have to be either a) incredibly dense, or b) trying, not to know under what terms they were licensed.
I think there is a world market for maybe five personal web logs.