This is what made RoboVM go comercial AFAIK, as they could hardly make a living from contributions.
My first Turbo Pascal for Windows was bought after a few months of saving. Same with other tools.
Even open source, I used to pay for the Walnut Creek CD-Roms.
Nowadays I still buy software tools and do occasional donations.
So I cannot understand how the millenials expect to get their tools for free on one side, but then complain that unless they are selling services or SaaS software no one pays them.
I'm a (senior) millennial and I'm prepared to pay for tools that are worth it. However, Free (as in freedom) software has come a long way, I won't pay for tooling that is at par or less capable than, with Free software. I think the rise of GPL/Open source - GCC, Linux and Free DBs & languages (and their ecosystems) are to blame; not millennials.
Also some people would keep on re-installing them past the demo deadline, or crack them, just to avoid paying.
But not on the scale that happens today.
Linux and GCC would not be as developed as they are if it wasn't for the companies that sell hardware and are willing to pay engineer time to improve them.
During GCC early days, most contributors were the ones not wanting to pay for the Solaris SDK, so its development was as fast as Hurd still is today.
Regarding languages, that is why commercial tools get all the nice goodies, no one can make a living of selling improved tooling to FOSS developers.
Hence why many watch a talk from Bret Viktor and are amazed of his presentations, but we already had such tools in 90's, they just had the sin of being commercial.
I mostly don't need the "nice goodies" - which why I don't but them (and I am prepared to buy when I do, or to show support to the developer. I love JetBrains).
> no one can make a living of selling improved tooling to FOSS developers
Good thing FOSS developers can improve their own tooling; they are developers after all. Freeware and Demoware are hardly comparable to Free & Open Source Software except on price. As a developer, I am empowered when I can fix bugs in my tools and submit a pull request upstream (happened to me 3 times this year alone). What do you do if you run into a bug in Borland Turbo Pascal or QBasic? If you have the energy, submit a bug report and hope it get fixed 4 versions down the line.
You don't see this entitlement to free tools in other professions.
I understand why you would license your software under this if you want to give end users the SW freedoms developers enjoy. I also understand why many makers of safety-critical devices avoid it like the plague.
Case in point, the automotive industry. Coincidentally, the Qt company has in past few years started engaging automotive companies [1][2]. The move to (L)GPLv3 can be valid and has other reasons besides pushing commercial licensing. But you can't say it doesn't have any impact on the industry.
[1] https://www.qt.io/qt-news/qt-company-launches-automotive-sui... [2] Spot the gauge needles and car body models in the announcement http://www.qt.io/qt5-7/
(Why they ship many of the more optional ones at all instead of embracing external providers like Homebrew or Macport continues to mystify and frustrate me)
If someone breaks their init with this replacement, Apple can always say "reinstall the OS". But if you're talking about a car that has crashed that's a different PR problem...
Btw. It's very easy to comply LGPLv3 in proprietary project if you want.
1) If you don't modify the Qt library and link dynamically there is no problem whatsoever.
2) If you modify the Qt library or link statically, it's enough to provide modified version of the Qt library and combined object files that make it possible to relink the application to different version.
Industry loves Qt. You either pay a little or spend little extra effort.