> Lesser GPL permits use of the library in proprietary programs
That means "in some cases", not "in all cases". Logical fallacy on your part.
> ordinary GPL for a library makes it available only for free programs
Here, GPL'ers contradict themselves (for both senses of "free"). GPL code can, technically, be non-gratis. And GPL code can be used in non-GPL programs (you just can't distribute them easily).
Somebody, please save RMS, write an Emacs mode that inserts spaces into JavaScript and converts single char names into made up longer ones! For extra bonus, insert comments that talk about how if you are not using GNU, you are a slave! A slave, I tell ya!
But your planting of a tree doesn't automatically prevent the farmer you bought the apple from from making any money.
If I have to release my code under GPL, I can't make money charging thousands for it (low volume type of app). If I can't make money from it, I won't spend years developing it. Not having the app would make it harder for some pharma scientist somewhere to cure cancer. Everyone loses. Communism doesn't work.
No. Whose object code? Is it talking about my object code or the library's?
Ten lines per function, per header, per library, per program?
Edit: I think you didn't understand LGPL yourself either. I think in the quoted lines, "object code" refers to your code, and accompanying them with a copy of GPL refers to having to release your code under GPL. Or do you think you only have to say you release it under GPL and not actually release it?
If, as you say, LGPL, is clear to you, what do you think "object code" refers to in the (b) clause you just quoted? How are the "ten lines" counted in the paragraph above (you didn't quote): separately or total? etc. etc.
That's what they want you to believe. Try reading the license.
You have to know how many lines from the header file you are "distributing" (in the GNU lingo). If you are using C++ templates, you are probably screwed. You have to make sure you link dynamically (or else). LGPL seems to require advertising the library. And if you want do static linking, talk to a lawyer. Linus and RMS disagree on what constitutes "derived work", btw.
Edit: I'd like to know what motivated people to upmod parent, when it's factually incorrect and can cost developers dearly if they take the message at face value.
> There are plenty of examples of successful companies that have used this model
Do you mean they used their blog as the main marketing effort? I'd like to hear more about those.
It seems if the users are looking at your blog, they've found you already. Or perhaps those companies created thousands of other blogs that were only used for search engine optimization (linking back to their money blog)? That I can understand.
> Lesser GPL permits use of the library in proprietary programs
That means "in some cases", not "in all cases". Logical fallacy on your part.
> ordinary GPL for a library makes it available only for free programs
Here, GPL'ers contradict themselves (for both senses of "free"). GPL code can, technically, be non-gratis. And GPL code can be used in non-GPL programs (you just can't distribute them easily).