3 ms·
There are a lot of devices out there - billions, in fact - that are not smartphones. There are a lot of devices that USE Qt today and do not have graphic accel
by joezydeco 16y ago
There are a lot of devices out there - billions, in fact - that are not smartphones. There are a lot of devices that USE Qt today and do not have graphic accelerators on them.
Qt's processor demands are happily keeping up with Moore's Law and the ability of new processors, leaving very little for the developers.
- wladimir 16y agoQT is trying to keep up with the state of the art in GUIs, which means flashy, animated, and a lot of eye-candy. This requires (relatively) heavy GPU power, hence the OpenGL requirement. That's a choice they made. They expect that by the time when Qt5 is ready, all customer-facing devices will have a decent GPU.
- joezydeco 16y ago"...by the time when Qt5 is ready, all customer-facing devices will have a decent GPU." Not by a long shot. There are stacks and stacks of legacy designs that use Qt/Embedded and will never have a GPU on them.
- wladimir 16y agoLegacy designs should probably use a legacy version of Qt. That's not an argument to keep Qt5 in the past forever. They rightly should look ahead instead of back.
- joezydeco 16y agoI'm cool with that too, but then Nokia/Trolltech should say so. The current position is "well, embedded users can use Qt Lighthouse" which doesn't mean a thing at this point. All the more reason to fork, as jsherer has noted right below this.