4 ms·

>QML is nice, but make sure you have the processor overhead for it. It's all javascript and the interpreter will suck up your processor time. What professor ov

>QML is nice, but make sure you have the processor overhead for it. It's all javascript and the interpreter will suck up your processor time. What professor overhead? It's 2012. Our quad core processors sit idle most of the time -- and even those in our phones aren't particularly challenged. Plus, what "interpreter"? For one, V8 uses JIT, second, it's way faster than Ruby/Python (languages that are also used for app development), and in Qt5 V8 is just the logic layer, the GUI/scene-graph parts are C++ and accelerated. For people doing lower-end embedded stuff Qt5 isn't going to give you much, if you can run it at all. Well, DUH! Who said anything about them? These people can't even afford to use Java or C#, much less V8 bindings for a UI toolkit, and even the C++ Qt5 part is not targeted to them anyway.

joezydeco 14y ago
"and even the C++ Qt5 part is not targeted to them anyway." Thanks for reinforcing my point. Qt5 is more of a smartphone platform than a GUI toolkit for embedded systems now. There are still a lot of low-end chips that need graphics toolkits and the new whizbang stuff just can't work on these systems. Don't tell me QML2 is great for prototyping GUIs when I can't even run it on my platform. I completely understand why the switch in focus came along, especially when Nokia took over. I still have bug reports from 2-3 years ago that have been marked "don't care, won't fix" by Nokia. My anecdata comes from actual years of experience making Qt work smoothly on lower-end hardware.