Wow, you seem right. That's incredibly dumb. It almost seems auto-destructive.
Wow, you seem right. That's incredibly dumb. It almost seems auto-destructive.
If car manufacturers would decide to support upgrading the Qt version by uploading shared objects directly to the car there would be no need for them to buy Qt Licenses. Because technically they could support all points of the LGPL. But that will never happen for two reasons:
1) It is very hard to get out of the contract if you already bought a license. You would have to prove that you aren't using any commercial tools anymore (of course they are the same tools as GPL but installed a different way).
2) They are car manufacturers and known to lock down their systems as much as possible.
The Qt Company probably didn't think about the average C++ Developer or Desktop programs at all while writing these Terms and Conditions...
You even require written permission from Qt to upgrade from LGPL to the Commercial License[0]. Because if you started programming without paying them their fees you probably owe them even more money according to them...
[0] https://www.qt.io/faq/tag/qt-commercial-licensing (If I have started development of a project using the open source version (LGPL), can I later purchase a commercial version of Qt and move my code under that license?)
Have you ever tried to explain the Qt licensing system to the legal department of an automotive, medical, or aerospace manufacturer? I have.
If you can get them to understand it, their faces turn white at the idea of the end customer sideloading new libraries into the device. The conversation pretty much stops there.