What is faster to write a GUI - Qt / C ++ (traditional approach) or Qt / WebKit / JQuery / HTML5 (browser application)?

Question

JavaScript

I write applications in Qt/C++ in the traditional style - classes, objects, widgets, signals, slots, etc.
I see that Qt is developing in all directions at once - HTML5, QML.
No wonder, I thought, that Qt is moving in these directions.
Now, when starting a new project, there are (big) 3 types available:
1. Qt GUI application
2. QtQuick application
3. HTML5 application Type
1 features I know. I don't know anything about the rest.
Maybe it's better to write GUIs on them, and in principle desktop applications? What are their advantages and differences?
Interested in the speed of application development as a whole, ease of support, flexibility, extensibility with third-party libraries.

Answer 1

Browser is faster.
There are no troubles with crosses (in JS you can stir up any OOP that you like best, plus there is CoffeeScript - you can use functionality), a lot of different frameworks - choose any one in which it is more convenient for you to work. Frameworks that were specially sharpened for this and only in order to develop gui was easy, convenient and fast.
The problem is that the application does not look native.
Partial solution - you make a browser application, and open it in QtWebKit - it starts to behave like a native one (frame, collapse, etc.).
Strongly not naoptimize - a complex gui will eat memory and slow down.
The problem is that if you don't understand what's good about JS and how to use it, you'll get worse than crosses. We have to delve into.
+ IMHO "HTML5" is a useless buzzword. The W3C has gone crazy and is doing some bullshit. Instead of expanding the capabilities of the encoder, it nails some kind of mess right into the browser. Surely this is the machinations of the damned DRMs. It is correct to say "application with a web interface".

Answer 2

It all depends on how the events will be thrown into the code. Once upon a time I made an interface on activex IE, it's still hell, and it also slows down too much, it will be a nightmare with a large amount of data, there are no virtual controls, you need to load all the data at once. There were no special problems with events, it was normally forwarded in C ++. But the interface is very unresponsive, the tables were several thousand rows long, sorting, etc. Everything was done on the C++ side, the DOM tree was constantly rebuilt.