Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Qt 6.6 and 6.7 Make QML Faster Than Ever: A New Benchmark and Analysis

qt.io

Post reply on HN
Print view View original

41–50 of 107 posts

Re: Qt 6.6 and 6.7 Make QML Faster Than Ever: A New Benchmark and Analysis

#41

Post by LorenDB »

turrini wrote: post #13
soundarana wrote: post #11

> Another thing you can immediately see is that the QML version of the algorithm is generally much slower than the JavaScript version. As noted above, this is due to it being built on QObjects rather than JavaScript objects. Of course, QML is trying to beat the browser at it's own game, but can't match the billions invested in browser performance. Qt classic is dead, and QML is a less featured, less documented, under…

Sorry, but this is FUD. Qt is miles ahead of Electron in terms of performance, app startup, native platform support, and low memory consumption, to name a few. Additionally, its documentation is one of the best in the market.

+1 on the documentation. As someone whose job involves a daily use of Qt, I think I've been spoiled by the documentation. Qt does a tremendous job of explaining nearly every function and property in detail, as well as giving a healthy class-level overview (often with code snippets and even screenshots where it might be useful). In fact, even their (many) example programs each have their own documentation page explaining what the example code ia doing.

Re: Qt 6.6 and 6.7 Make QML Faster Than Ever: A New Benchmark and Analysis

#42

Post by blackpill0w »

nine_k wrote: post #26
lmm wrote: post #21

Earlier quoted context omitted.

> even if I can write some GUI in a "rusty" way, it won't suddenly speed up things because GUI is almost never a bottleneck. Nor are any of the other things people use Rust for, but that doesn't seem to reduce the enthusiasm any.

Rust does not make your rocket fly faster, but it lowers the chance that it would explode mid-flight.

Rust can also leak memory (memory leaks are memory safe in Rust).

Re: Qt 6.6 and 6.7 Make QML Faster Than Ever: A New Benchmark and Analysis

#43

Post by speed_spread »

singularity2001 wrote: post #37

Does anyone else think that QT is mostly overkill and HTML is good enough in most cases?

Funny because I think HTML is overkill and QT is good enough. HTML meaning that your app runs in a browser, which generally uses much more resources than a QT app.

Re: Qt 6.6 and 6.7 Make QML Faster Than Ever: A New Benchmark and Analysis

#44

Post by amelius »

simion314 wrote: post #34
amelius wrote: post #28

Earlier quoted context omitted.

It would make sense to have a library that can do basic Svg/Canvas things, in Rust. From there, people can write all sorts of GUI libraries.

Yeah but Qt does a lot more, to match Qt you would need a similar effort. I remember some time ago was a popular article shared here on how hard it is to render text when you need to consider all the languages and all the font types and all the options. So it wold be easy to paint some shapes and some english text in the happy case and it would probably be enough for video games but then you need Widgets that will wo…

The point is if you start with a good foundational layer, then a community can build greater things on top of it.

Of course, it will take time and if you're looking for a great library that can do everything out of the box, now, then you should pick Qt, there's no doubt about that.

Re: Qt 6.6 and 6.7 Make QML Faster Than Ever: A New Benchmark and Analysis

#45

Post by not_the_fda »

soundarana wrote: post #11

> Another thing you can immediately see is that the QML version of the algorithm is generally much slower than the JavaScript version. As noted above, this is due to it being built on QObjects rather than JavaScript objects. Of course, QML is trying to beat the browser at it's own game, but can't match the billions invested in browser performance. Qt classic is dead, and QML is a less featured, less documented, under…

Qt Widgets is not dead, its feature complete and in many industries that's a very valuable. New projects in Qt widgets are being done all the time in the embedded space.

Re: Qt 6.6 and 6.7 Make QML Faster Than Ever: A New Benchmark and Analysis

#46

Post by simion314 »

amelius wrote: post #44
simion314 wrote: post #34

Earlier quoted context omitted.

Yeah but Qt does a lot more, to match Qt you would need a similar effort. I remember some time ago was a popular article shared here on how hard it is to render text when you need to consider all the languages and all the font types and all the options. So it wold be easy to paint some shapes and some english text in the happy case and it would probably be enough for video games but then you need Widgets that will wo…

The point is if you start with a good foundational layer, then a community can build greater things on top of it. Of course, it will take time and if you're looking for a great library that can do everything out of the box, now , then you should pick Qt, there's no doubt about that.

You need a big community that can build a Qt alternative, we have Linux as an example of a community project but the reality is there was a lot of money behind it, so you need a Rust community with a lot of money behind it so developers will be paid to work on the non-cool stuff.

Re: Qt 6.6 and 6.7 Make QML Faster Than Ever: A New Benchmark and Analysis

#47

Post by saidinesh5 »

mardifoufs wrote: post #31

What's the QML story when using pyside6/pyqt? I know it's possible to use both but I was wondering if it's worth it, and how painful it is to add to an existing app?

If your existing app is a pure CLI app, you just expose your Qt objects to qml and it should be fairly smooth sailing.

If your existing app is a QWidgets app, then not sure how much benefit you'd have when mixing QML/QtQuick with your QWidgets side of things. We did implement such a thing at a little project before... where the "canvas of items" was written in QML and the remainder of the UI was QWidgets. For our usecase, it was good.

Re: Qt 6.6 and 6.7 Make QML Faster Than Ever: A New Benchmark and Analysis

#49

Post by JanisErdmanis »

sircastor wrote: post #29

In my last role we were using QML as a prototyping tool for interfaces, and basically making whole proof-of-concept apps in it. It is immensely powerful once you get the hang of it. Though if anyone is thinking about it, please note that it is not (or wasn't) really a language on its own. It's meant as a UI complement for Qt, and trying to build stuff exclusively in QML is a recipe for tears.

Can you elaborate on “recipe for tears”?

Re: Qt 6.6 and 6.7 Make QML Faster Than Ever: A New Benchmark and Analysis

#50

Post by guappa »

amelius wrote: post #44
simion314 wrote: post #34

Earlier quoted context omitted.

Yeah but Qt does a lot more, to match Qt you would need a similar effort. I remember some time ago was a popular article shared here on how hard it is to render text when you need to consider all the languages and all the font types and all the options. So it wold be easy to paint some shapes and some english text in the happy case and it would probably be enough for video games but then you need Widgets that will wo…

The point is if you start with a good foundational layer, then a community can build greater things on top of it. Of course, it will take time and if you're looking for a great library that can do everything out of the box, now , then you should pick Qt, there's no doubt about that.

But who'd contribute when qt is already there?

Getting contributions is nearly impossible. Getting them for a not so useful vanity project is probably impossible.

Post reply on HN