I'm partly responsible for technology selection at one of their larger commercial customers, and I do care and worry quite a bit (and have also shared these opinions in a customer keynote at their last internal sales conf). Upsetting the open source community has been shrinking the talent pool to hire from considerably; it's where your next senior devs/SMEs really get educated on a technology. The non-FOSS LTS has increased integration cost and complexity for us. The divergence between easy to instantiate developer desktops (i.e. Qt from distro) and what we carry in the product is also a headache. It also makes it harder for internal champions to argue for Qt, because open source solutions are very popular and this differentiator is now in widespread doubt.
Business has been growing for them, but this isn't always necessarily on the strength of the product alone, but can also be a combo of inertia and fortuitous circumstances. For example, within the automotive industry the trend has been to merge multiple ECUs into fewer and consolidate technology stacks, and this has counter-intuitively probably resulted in quite a few sales as the OEMs move e.g. instrument cluster UIs from boutique solutions like Kanzi to the Qt stack they already used on the headunit (which is swallowing those other ECUs), or adding on more licenses for QNX guests. That doesn't mean the same customers aren't also already moving part of their HMI to Flutter/Unity/Unreal as the next thing rather than contemplating the port to Qt 6, however.
It's also that making moves to monetize existing customers more does work. For a time.
The effects of strategy changes like this can take many years to become apparent.
Business has been growing for them, but this isn't always necessarily on the strength of the product alone, but can also be a combo of inertia and fortuitous circumstances. For example, within the automotive industry the trend has been to merge multiple ECUs into fewer and consolidate technology stacks, and this has counter-intuitively probably resulted in quite a few sales as the OEMs move e.g. instrument cluster UIs from boutique solutions like Kanzi to the Qt stack they already used on the headunit (which is swallowing those other ECUs), or adding on more licenses for QNX guests. That doesn't mean the same customers aren't also already moving part of their HMI to Flutter/Unity/Unreal as the next thing rather than contemplating the port to Qt 6, however.
It's also that making moves to monetize existing customers more does work. For a time.
The effects of strategy changes like this can take many years to become apparent.