4 ms·
Everything in this release says Qt/Embedded is dead and it's all about trying to stay relevant on smartphones. Small platforms need GUIs too, and there's just n
by joezydeco 16y ago
Everything in this release says Qt/Embedded is dead and it's all about trying to stay relevant on smartphones. Small platforms need GUIs too, and there's just not enough MIPS on those platforms to handle QML and it's Javascript interpreter and all the other crap that goes with it. QML is a dog on anything below 700 MHz.
"Qt will require OpenGL (ES) 2.0 to work."
Sigh... Guess we're all using 4.7/4.8 forever.
- jsherer 16y agoI see a Qt fork coming that maintains the current approach for the future of the 4.x line.
- danieldk 16y agoThey are moving to open governance. So, why not make use of it and let your voice be heard before going through the enormous effort that a fork will be?
- nakkiel 16y agoThey are loosing the unixes too. This has always been a big winner for Qt. What toolkits run on most operating systems? There sure aren't many of them and they mostly suck.
- pavlov 16y agoI wouldn't write off Qt/Embedded just yet. Nokia has regularly made noises about their wish to eventually use Qt on Series 40. Series 40 is their dumb-/featurephone OS. It powers most of the billion phones that Nokia sells yearly, and it's not set to be replaced by Windows Phone. There's no way OpenGL ES will make an appearance on those devices for a long while. The Qt 5 announcement made a point of emphasizing maximum source compatibility between Qt 4 and 5. It seems likely to me that Qt 4 will still see some development from Nokia.
- joezydeco 16y agoSo you're going to try and run V8 on a Series 40 class processor? This is just getting silly.
- jerf 16y agoPavlov is clearly implying they must have plans not involving all that heavyweight stuff on low-end devices, not that they're going to just jam it on anyhow.
- pavlov 16y agoYeah, that's it -- I guess my point was not very well articulated. To be clear, I think Nokia is going to maintain an active branch of Qt 4.x for Series 40, and that work will benefit Embedded Linux as well.
- wladimir 16y agoNah, how long will smartphones remain below 700MHz? QT5 is planned for the future, it's not like it is released now. By the time it is ready, I don't think speed and OpenGL ES 2 support is still an issue on devices by then.
- joezydeco 16y agoThere 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.