Remember, it's not fair to yourself to compare toolkits based solely on desktop environments that use them. I'm sure you could create a memory-hungry DE with EFL, if you do it wrong.
Qt has been used for a long time in the embedded space due to its performance and portability. Take Qt on QNX (Blackberry 10), and many of the new mobile iterations of Linux since Meego. This was originally Qt made to run specifically on underpowered devices in very limited environments, and it did pretty well given the constraints.
With the proliferation of cheap ARM devices that are more powerful than desktops from 10 years ago, there are increasingly less reasons to be concerned about targetting the traditional low-end of sub-128 MB RAM PCs without minimal hardware acceleration for graphics. I think Qt has done plenty to prove itself, while GTK 3 still has a ways to go on mobile. Of course, if you have very specific needs that only GTK 3 addresses, go for it.
Qt has been used for a long time in the embedded space due to its performance and portability. Take Qt on QNX (Blackberry 10), and many of the new mobile iterations of Linux since Meego. This was originally Qt made to run specifically on underpowered devices in very limited environments, and it did pretty well given the constraints.
With the proliferation of cheap ARM devices that are more powerful than desktops from 10 years ago, there are increasingly less reasons to be concerned about targetting the traditional low-end of sub-128 MB RAM PCs without minimal hardware acceleration for graphics. I think Qt has done plenty to prove itself, while GTK 3 still has a ways to go on mobile. Of course, if you have very specific needs that only GTK 3 addresses, go for it.
Comment