The decision will eventually alienate OS community which will force current 
licensees consider the viabilty of the platform for their next generation of 
products. There is a lot of air in the QtC stock price as a result of the new 
licensees and how well Qt/Qml fits the needs. I certainly hope that the 
decision will be reconsidered before any of the big licensees switches to react 
native.
As a Qt and React developer I can say that the entry barrier is high but at 
least Facebook is certainly more predictable platform provider than a single 
Finnish company from strategic infra investment standpoint.

I am not a license holder and am a long time critic of QtC licensing to 
startups.

And I love Qml

> Jyrki Yli-Nokari <jyrkiylinok...@gmail.com> kirjoitti 13.5.2021 kello 10.22:
> 
> The decision will eventually alienate OS community which will force current 
> licensees consider the viabilty of the platform for their next generation of 
> products. There is a lot of air in the QtC stock price as a result of the new 
> licensees and how well Qt/Qml fits the needs. I certainly hope that the 
> decision will be reconsidered before any of the big licensees switches to 
> react native.
> As a Qt and React developer I can say that the entry barrier is high but at 
> least Facebook is certainly more predictable platform provider than a single 
> Finnish company from strategic infra investment standpoint.
> 
> I am not a license holder and am a long time critic of QtC licensing to 
> startups.
> 
> And I love Qml
> 
>> André Somers <an...@familiesomers.nl> kirjoitti 12.5.2021 kello 22.22:
>> 
>> 
>>> On 12-05-2021 17:51, Thiago Macieira wrote:
>>>> On Wednesday, 12 May 2021 08:30:52 PDT Frank Hemer wrote:
>>>>> On Mittwoch, 12. Mai 2021 17:26:50 CEST Thiago Macieira wrote:
>>>>>> Even maintainers who like me don't get access to the source, it's
>>>>>> important
>>>>>> to know the release was made.
>>>>> Not having access to sources for maintainers is simply ridiculous.
>>> The problem is licensing, not Qt Company's willingness. They offered when 
>>> this
>>> all began. But since it's not open source, I can't look at it.
>>> 
>> When then means that QtC is committing things into modules without that 
>> modules' maintainer being able to look at it for legal reasons. Ridiculous 
>> indeed. It would make me question (had I been a maintainer, which I am 
>> certainly not) if I'd want to keep that hat on at all.
>> 
>> André
>> 
>> 
>> _______________________________________________
>> Development mailing list
>> Development@qt-project.org
>> https://lists.qt-project.org/listinfo/development
_______________________________________________
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to