The problem is typically people not bothering to understand the L in LGPL.
You're missing the whole point.
It's irrelevant whether projects should have a budget or not.
The whole point is that there are plenty of alternatives that do not require thousands of dollars per year*developer, nor do require lawyers to audit releases.
On the desktop you can go Electron, but you then pay penalties in performance that not everyone is willing to endure.
In the embedded space there is little or no alternative.
The actual LGPLv3 text has zero instances of the word "commercial" or the word "consumer" so interpretation is all we can go by.
> A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling.
The FSF felt that consumers needed protected from tivoization but commercial users did not since they had the financial resources to fight for themselves with contract law.
The FSF felt that consumers needed protected from tivoization but commercial users did not since they had the financial resources to fight for themselves with contract law.
The anti-tivoization clauses mean you need to provide a way to install user-built Qt libraries on the target device. You might think that's not a big deal until you go to work for an automotive or medical company and meet up with the massive wall of lawyers that tell you no fucking way.