Let me repeat in case it was an honest oversight:
Number of deployed smarphones with Qt: Tens of millions of Symbian devices (+ some N900, N9, and N950).
Number of deployed smarphones with EFL preinstalled: Zero.
Number of mobile platforms Qt runs: 7 (Android, GNU/Linux, iOS, OSX, QNX [=Blackberry 10 and Playbook OS], Symbian, Windows 8 [x86 tablets].
Number of mobile platforms EFL runs: 1 (GNU/Linux)
[GNU/Linux = Non-Android Linux variants like Ubuntu, MeeGo, etc.)
The numbers are not lying: Of the alternatives that are not bound to a specific vendor (as in Apple, Google, MS) Qt is the only viable alternative for native apps.
Qt experienced developers to write apps are available en masse because of Symbian.
So even IF Qt5’s pure drawing performance was somewhat lower than EFL’s, in this market a vendor can't be picky.
Samsung could easily choose EFL because the indication is that Tizen is focused on web apps written for WebKit. EFL has next to no developer base and convincing developers to learn a completely new toolkit is a hard task.
The N9 was actually even so successful, it resulted in the so-called N9 Bounce: In a time when Nokia’s Elop-caused revenue fell like a rock, the N9 caused an upward bump in Nokia’s sales: http://communities-dominate.blogs.co...41902ae970d-pi
(Source: http://communities-dominate.blogs.co...-elop-now.html )
I don't know what Attachmate has to do with this. Are you confusing Attachmate with RIM who are launching Qt-based BB10 devices this very month? http://blog.qt.digia.com/blog/2012/1...rting-program/
I find it hard to believe that he has no clue how to at least somewhat fairly compare memory sizes for toolkit (he's a developer after all). This looks more like a deliberate tactic. For someone like him who knows this stuff, it's so very easy to write a simple app that draws an X amount of pre-defined lines on screen and then print an output how long that took and how much memory it required.