On Mon, Mar 22, 2021 at 2:51 AM Jason H <jh...@gmx.com> wrote: > > > > > > Licensing FUD + death-of-perpetual-license + death-of-OpenSource-LTS + > > > Qt-6-rolling-out-incomplete + deleted-convenience-methods = > > > customers-leaving > > > > I wonder if the loss of confidence in the current Qt owners can ever be > > compensated. > > > > Even if TQC took back their critical decisions, I can't imagine that people > > would ever > > trust them again. This could cause fatal damage to Qt in the long run if > > they don't sell > > it to someone more responsible. > > Is there anything we can do to maybe block the release of new Qt versions, so > that the BSD poison pill clause is triggered? Then we can start over from a > BSD license, and maybe get other custodians of the code base? > > Qt is currently catering to automotive companies, and those sales allow them > to neglect other markets. I hope they circle back and get there market > segments they have been neglecting. > > My company abandoned commercial use of Qt as we were in a neglected market > segment... Rewrote the app native on each platform. It was painful, but > stuffiness routing the band-aid off quickly is the way to go. I've been > lurking hoping to hear good things about QT6 but it looks like The decision > to go native was the right one.
Jason, welcome to the club of re-writers. Are you still using it for mobile platforms? Kind regards, Robert _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
