5 ms·
As an enthusiastic Qt/Embedded developer, I'm hopeful. Qt/Embedded suffered under Nokia. QML, nice as it is, is a dog on anything less than 700 MHz of core.
by joezydeco 16y ago
As an enthusiastic Qt/Embedded developer, I'm hopeful.
Qt/Embedded suffered under Nokia. QML, nice as it is, is a dog on anything less than 700 MHz of core. Strings flying everywhere. The Trolls were told to put everything into QML and Mobility, to the point where I've filed embedded bugs and been told "Sorry, it's not a priority issue".
Add this to the word I got through the backchannels that Nokia was discouraging (and not even testing) static builds of Qt libraries and I could see the writing that Qt was pretty much completed for non-QML embedded devs.
I'm hopeful that wherever the code lands next that we'll see some of the floors get swept and we can all move on. Lighthouse is a nice gateway to better things, for example.
- gmartres 16y agoYes, especially since Mobility really is a weird beast. See http://doc.qt.nokia.com/qtmobility-1.1.0/gallery.html http://doc.qt.nokia.com/qtmobility-1.1.0/gallery.html . Maybe it's just me but this screams "over-engineered", I still haven't figured how you're supposed to use it.
- joezydeco 16y agoI agree. My take on Mobility is that they needed a higher level of abstraction to make QML attractive to Javascript/Cocoa Touch/Android XML developers.