If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Edit: from their website, I see that the "speed" thing is about ***BOOT*** times, not actual performance. You know that you can make Android boot in less than half the time by deleting stuff? They say regarding the point of the project "Android brings in a lot of additional stuff, but that is also the point. Most embedded devices do not need that." -- well then don't build them into your Android build. Its pretty easy to customize a build to leave out all the stuff you don't need, and I say this as someone who develops embedded systems (and uses Android, for the most part).

Comment

Possibly. Qt5 took in some of the "KDE-Only" things and KF5 should be replacing some of the other "KDE-only" things with native, generic Qt ones. While this particular project's source is closed, the idea is not. Its possible that we could see ROM's (Maybe CyanogenMod ) offering versions that boot to a Plasma Active interface based on the ideas of "Boot-To-Qt"

Comment

Well, I am not sure this is the case. The Qt source is available under a free license, so I believe you will be able to build this yourself. Of course, it's a tech preview, so not all of it may be released yet. But the basic idea of the dual licensing model is that Digia provides stuff ready-made (compiled, adjusted to the device, etc.) to commercial parties who pay Digia for this bundle together with a support license. If you don't want support, just build it yourself. Of course, I might be wrong and there might be closed-source code in there somewhere, but I haven't seen any statement suggesting this. So I believe that the Phoronix article is wrong.