Re: [Interest] Another Qt disappointment

2021-05-04 Thread Bernhard Lindner

> I don't know how they can sleep at night. 

I guess Uncle Scrooge would argue that you can sleep very good on a mattress 
stuffed with
banknotes, no matter where the money came from ;-D

I agree to all of your statements.

-- 
Best Regards,
Bernhard Lindner

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Another Qt disappointment

2021-05-04 Thread Jason H
And me as well. 

 

At what point is Qt no longer considered open source? As someone who has been using Qt professionaly since 3.3.3, I have a hard time considering it 'Open Source" anymore. It's basically the most closed opensource project I know of. While I have not really contibuted to the project in terms of lines of code(I've been maonly a bug reporter) and multiple commercial licensee, I am now leery to do so beccause it's basically be free work for Digia, which they wll probably just change the license on later, anyway. At one time I would have loved to worked on Qt for my job, but not anymore. 

 

Qt reached the pinnacle of openess when Nokia LGPL'd it, and it's been downhill ever since. 

 

The continued screw-tightening by Digia makes Qt harder for me to use even in my own personal, non-distributed, non commercial projects. 

 

I do think Qt is technically great but the behavior of Digia makes the product unattractive. 

 

I don't know how they can justify the change to commercial providing of a LTS release. That's just blantaly evil/bad/whatever. I don't know how they can sleep at night. 

 

IMHO, Digia will continue to inconvenience users to the point of forcing them to use git repos only, not realizing that every other open source project makes it trivial to use with their own package manager (npm, pip, etc).  (Sorry if that gave them ideas, but they would have iterated to that eventually)

 

I wonder if any of the engineers are pushing back internally?

 

 
 

Sent: Tuesday, May 04, 2021 at 9:53 AM
From: "Bob Hood" 
To: interest@qt-project.org
Subject: Re: [Interest] Another Qt disappointment

On 5/3/2021 8:44 AM, Jason H wrote:

I have a load cell. It's a sensor that measures weight. I wanted to make a quick UI for it in Qt.
That went as expected. Then I wanted to put the app on a spare Amazon Fire tablet rather than tie up a computer with it.

I was running with Qt 5.15.2, but there's. bug with Bearer in Qt 5.15.2, so I went to update it, and lo and behold, there is no 5.15.3. It's apparently, commercial-only. So I figured I'd finally update to Qt 6, except that after installing, it turns out Qt 6.0 doesn't have androidextras.

It's not just me that is disappointed, everyone in the comments at https://www.qt.io/blog/commercial-lts-qt-5.15.3-released seems disappointed that 5.15.3 is commercial-only.

So as I sit here waiting for Qt 6 and Qt 5.15 to uninstall, and Qt 5.12 to install, I figured that I'd drop this note about how things are going the wrong way.


I believe the post in early January (titled "Qt 5.15 pull out of open source?!") made a similar observation, and served as the snowball which ended with the late unpleasantness.

Let's be real: It was a blatantly stupid decision to cut off open source support within the production 5.15 line.  Compound that with some of the licensing decisions made with Qt6, and it leaves me, both personally and professionally, with a distrust of TQC's road map for Qt.  I'm hesitant now to base any software designs on it because of this new baggage.
___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Another Qt disappointment

2021-05-04 Thread Bob Hood

On 5/3/2021 8:44 AM, Jason H wrote:

I have a load cell. It's a sensor that measures weight. I wanted to make a 
quick UI for it in Qt.
That went as expected. Then I wanted to put the app on a spare Amazon Fire 
tablet rather than tie up a computer with it.

I was running with Qt 5.15.2, but there's. bug with Bearer in Qt 5.15.2, so I 
went to update it, and lo and behold, there is no 5.15.3. It's apparently, 
commercial-only. So I figured I'd finally update to Qt 6, except that after 
installing, it turns out Qt 6.0 doesn't have androidextras.

It's not just me that is disappointed, everyone in the comments at 
https://www.qt.io/blog/commercial-lts-qt-5.15.3-released seems disappointed 
that 5.15.3 is commercial-only.

So as I sit here waiting for Qt 6 and Qt 5.15 to uninstall, and Qt 5.12 to 
install, I figured that I'd drop this note about how things are going the wrong 
way.


I believe the post in early January (titled "Qt 5.15 pull out of open 
source?!") made a similar observation, and served as the snowball which ended 
with the late unpleasantness.


Let's be real: It was a blatantly stupid decision to cut off open source 
support within the /production/ 5.15 line.  Compound that with some of the 
licensing decisions made with Qt6, and it leaves me, both personally and 
professionally, with a distrust of TQC's road map for Qt.  I'm hesitant now to 
base any software designs on it because of this new baggage.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest