throwaway546456's comments

I think combination of JUCE/IntelliJ pricing and Unreal Engine model would be a sweet spot:

1) Personal License - free if <50k annual revenue

2) Startup License - keep current price (500usd/month) but

a) allow 1 month subscription commitment instead of paying 1 year upfront

b) when subscription not get extended you should still be allowed to distribute product that is not updated

c) if you payed for 1-2 years of subscriptions and cancelled subscription after 1-2+ year, you should be able to keep using the version of Qt the moment when you first signed for .

3) allow Startup to choose another licensing option. Instead of paying upfront licensing fee, just allow paying annually 5% of revenue from products that keep using Qt.

It seems they dropped ball on mobile devices (iOS/android). In last few years they where mostly focusing on embedded, automotive and desktop. I wish they provided more indie friendly alternative license for mobile market something similar like Unreal Engine had e.g. taking ~5% of your revenue.

I know they recently provide 'small company license' and ~500usd/year is justified as long it's just hobby project if only your as a dev. The moment you reach $250k as a startup and have to hire few devs and pay $5k/year per each developer is making this less affordable. On top of that if you focusing on mobile devices (android/ios) probably you would need to have Felgo license (to cover some Qt limitations) which is crazily even more expensive.

At this point in few years Flutter, ReactNative, Unity, Unreal Engine and Electron will be slowly stealing more of Qt market.

why not use a gyrocopter then? It's cheaper, easier to maintain and more safe. Even if they are not that fast you don't have to get stuck in traffic jam, wait on traffic lights in the city and can flight directly with straight line from A to B.

good first start. What I still would like to see extra:

* option to notify user certificate got revoked. Short description why twitter style and link to details and give user choice to quarantine it or to still use it. This is in similar style what antiviruses do it telling you: 'this kind of malware name was potentially found but if we are wrong feel free to remove from quarantine'.

* revocation list is checked twice a day locally on the machine and twice a week (always on the same days) the current way remotely to strike a good balance as a default. Allow user to adjust frequency.

the slides are from 2016. I'm wondering how performance comparison would look like these days with metal or vulkan rendering backends.