2 ms·
As someone that develops in Qt for lower-end embedded systems, it's even worse. QML was a dog when you ran on anything slower than ~500 MHz and had all kinds o
by joezydeco 15y ago
As someone that develops in Qt for lower-end embedded systems, it's even worse. QML was a dog when you ran on anything slower than ~500 MHz and had all kinds of stuff bound to the frontend, mostly because of the script core. Now that the script core is going to need V8? That's gonna tank my CPU even more, if I can even get it cross-compiled for my target.
I'm not even sure how this dovetails with QWS being deprecated for Lighthouse. I've given up trying to understand Qt's roadmap post-Nokia and how it relates to my designs. I might be stuck with 4.8 forever.
- sho_hn 15y agoKeep in mind that QML in 4.8 is doing software rasterization while QML in Qt 5 is running via OpenGL ES on the GPU. And yes, that does matter, since making it easy to accelerate is the entire point of going declarative.
- joezydeco 15y agoBut the Javascript interpretation and C++ binding is still taking place on the core CPU. Some of the biggest lag I've seen is when object properties bound to C++ need updating. I'm sure GLES rendering will be great for mobile systems. Will rasterization under Lighthouse for old QWS deployments get the same attention and optimization? I don't see any interest from the developers in that area. Haven't seen it for years now.