[Interest] Does it really worth it?

[DAV]

Hello.
Qt always was and is a patron of KDE and KDE is a huge part of Linux.
So, I personally am don't think that Qt will die, at least in near future
(>5 years).
The worst thing could happend is transformation of Qt into less portable
framework
(only for desktops) but it will be a live in KDE anyway.

--------------------------------
Best regards, Dmitriy.



27 марта 2012 г. 15:34 пользователь DAV <dav.daemon at gmail.com> написал:

> Hello.
> Qt always was and is a patron of KDE and KDE is a huge part of Linux.
> So, I personally am don't think that Qt will die, at least in near future
> (>5 years).
> The worst thing could happend is transformation of Qt into less portable
> framework
> (only for desktops) but it will be a live in KDE anyway.
>
>  --------------------------------
> Best regards, Dmitriy.
>
>
>
> 27 марта 2012 г. 14:40 пользователь <josemaria at gomezvergara.es> написал:
>
> I would like to dedicate all my energy to only one technology during the
>> next 3 years. I was thinking to do a useful thing and to be honest I was
>> thinking in doing some kind of a good chart library for Qt. The thing is
>> that I dont really sure if Qt has a really good future.
>>
>> I mean. Nokia bought it but when everybody was expecting how nokia was
>> going to use it in their mobiles and tables, they left it and took
>> Microsoft for that. Now, it is a open project, what is good, but my
>> question is... how can I know if Qt will be alive in 2015? Should I
>> dedicate energy to create some kind of http://www.steema.com/teechart/vcl
>> .
>> Do you think that there is customers enough to support it?
>>
>> Thanks in advance for your time and opinions
>>
>> _______________________________________________
>> Interest mailing list
>> Interest at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20120327/eeedaeeb/attachment.html>