Thoughts on Qt World Summit Agenda
-
I was out of the loop for a while: 2012 at Berlin was the last event of that kind I visited. Back then, it was still "Qt Developer Days". So obviously, things have changed in the meantime, and I'm never one to say that things have to (or even should) stay the same.
Still, from the perspective of a Desktop-oriented software engineer, I no longer feel invited by the agenda on offer.
30 minutes for the Qt roadmap, but 80 minutes of customer cases and related talks, and no choice in that matter (other than go grab a coffee and do networking).
Lots of talks on the design offering and on the QA offerings, but not even a single technical talk on C++ developments. And many of the technical-oriented talks there are focused on embedded platforms.Sure, I understand. Desktop is just one of many platforms on offer, and no longer the most profitable one, I'm sure. Design and QA offers more opportunity to sell extra licenses. In that way, the World Summit feels like half a sales events. And more geared towards decision makers with deep pockets than lowly developers.
And it seems to indicate the Qt Framework itself has entered the "Stable" phase, and we can expect bugfixes and little more, as the Qt Company focuses its energies on more profitable areas.
-
Sad to read this,
I study mechanical engineering and because classical stuff is boring, I started to get into software, AI and so on.
I have to dig into PySide6 with QtQuick 2 because part of my bachelor thesis is to migrate an existing software from C# to python and do some image processing.My experience as a beginner with the Qt framework is not as good as i think it should be:
-
Qt works very well if you use Qt Creator/ Qt Designer to draw a ui and implement the buisiness logic in C++. It is well documented and i could resolve any issue by reading the docs.
-
Using Qt with python is a different thing. Very often i get into trouble. Rendering a QML is not a thing but keep it updated makes me trouble.
Documentation is very often auto-translated from C++ without examples.
Internet is full of old examples which are mostly written in PyQT widgets.
I'm ready to invest more time in Qt to get more experience in every possible language they offer. Firstly i thought it would be a good thing if Qt would offer their framework for Rust.... but after this experience with pyside6: I hope they won't.
I was desperate enough to get a QtAcademy - Account. Just nto find out that the content doesn'tz bring me any further.
-
-
@Asperamanca said in Thoughts on Qt World Summit Agenda:
30 minutes for the Qt roadmap, but 80 minutes of customer cases and related talks, and no choice in that matter (other than go grab a coffee and do networking).
Lots of talks on the design offering and on the QA offerings, but not even a single technical talk on C++ developments. And many of the technical-oriented talks there are focused on embedded platforms.It sounds like you were looking at the agenda for the Keynote Day (Day 1). What do you think of the agenda for the Breakout Sessions (Day 2)? Particularly the "Development Minds" stream.
And it seems to indicate the Qt Framework itself has entered the "Stable" phase, and we can expect bugfixes and little more, as the Qt Company focuses its energies on more profitable areas.
I wouldn't say that. Every minor release is still getting new modules (including the upcoming Qt 6.6), and there's a giant epic about modernizing C++ (https://bugreports.qt.io/browse/QTBUG-99243 -- this one is about C++20, and once this list is done it's probably C++23's turn)
Qt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches
-
@JKSH
Of course, I have exaggerated in some ways. Day two is more interesting. I'd be especially excited about- Qt Quick: Tips and Tricks
- Recent changes of the QML language
- Advances in Lower Level 2D/3D Graphic Enablers
- Understanding the Qt Stack Trace (but that one collides)
and while I won't need it in the near future, I'd also be interested in the talk about Interprocess Communication.
What about the others?
- Design track: Already evaluated and rejected, simply doesn't work well if the designer is an external
- QA track: We have used Squish for more than 10 years, and are now moving away from it because of technical and licensing issues, so doesn't make sense to look at further tools
- I don't do embedded development, so talks covering Boot2Qt and MCU are perfectly fine, but not for me
...and there are always going to be single talks that simply don't fit your needs or interests, which is why it makes sense to have multiple tracks.
So in total, across the two days, I'd have between 3 and 4 hours of talks I am interested in. It feels too little to make the trip worthwhile.
As for Qt framework, yes, I see a lot of rounding off. And just keeping things running is certainly a lot of work. But new developments in the scope of Quick/QML or RHI....?
If there were, I doubt they could fit the roadmap into 30 minutes.
