4 ms·

As for GTK3, rendering performance, latency and memory usage in QT5 suffer significantly. QT4 is not light, but QT5 adds overhead for no reason. I like the gen

As for GTK3, rendering performance, latency and memory usage in QT5 suffer significantly. QT4 is not light, but QT5 adds overhead for no reason. I like the general polishing in the core modules, but I have really no use for qtquick. For this reason, I really encourage anyone to get onto copperspice (http://www.copperspice.com/ http://www.copperspice.com/). Without MOC, QT really feels an awesome API.

ultramancool 11y ago
While I can't say I've experienced any significant memory usage or latency issues (possibly because I'm targetting recent hardware and working with large volumes of data), I'm completely in the same boat with QtQuick and CopperSpice does look quite interesting, I'll have to check it out.
joezydeco 11y ago
I use Qt a lot on smaller embedded targets and I haven't moved to 5. Don't really want to mess with the new windowing system and I can't put Wayland/Weston on a lot of my smaller projects. I'm pretty much locked into 4.8 (and it's eternally open tickets) for life.
- witty_username 11y ago
  > Wayland/Weston on a lot of my smaller projects Huh? Qt5 doesn't require Wayland; I've used it on X.
- turrini 11y ago
  Qt5 doesn't require Wayland, I'm using Qt 5.5.1 with widgets on embedded environments (X11 included) without problems.
  - joezydeco 11y ago
    X11 included Yeah, um, not possible for me. I use the Linux framebuffer and that's it.
  - deleted 11y ago
    [deleted]
- turrini 11y ago
  And it does support Linux FrameBuffer. http://doc.qt.io/qt-5/embedded-linux.html http://doc.qt.io/qt-5/embedded-linux.html
  - ultramancool 11y ago
    The thing to note here is that the stripped out the windowing system implementation for embedded machines. So if you're using framebuffer without X11 or Wayland you're on your own for windowing now, which was previously provided in Qt4. That's my understanding at least, I don't use Qt on embedded platforms though, can anyone confirm this?
    - joezydeco 11y ago
      That's my understanding as well. I haven't looked deep enough into the QPA stuff to understand it.
    - slavik81 11y ago
      I don't work on embedded platforms, but it seems Qt5 supports directfb, which can do windowing. http://doc.qt.io/qt-5/embedded-linux.html http://doc.qt.io/qt-5/embedded-linux.html http://stackoverflow.com/a/21489384/331041 http://stackoverflow.com/a/21489384/331041
jabjoe 11y ago
Yes, MOC and QT's C+++ is really an awful thing. Copperspice being just normal C++ is interesting. Have to see what happens. But for me, C is where my heart is, so there is still two + that need to go for me. ;-)
rhodysurf 11y ago
Whoa thanks for pointing out copper spice! I use Qt everyday at work and this could be cool to mess around with for some projects.

ultramancool 11y ago

While I can't say I've experienced any significant memory usage or latency issues (possibly because I'm targetting recent hardware and working with large volumes of data), I'm completely in the same boat with QtQuick and CopperSpice does look quite interesting, I'll have to check it out.

joezydeco 11y ago

I use Qt a lot on smaller embedded targets and I haven't moved to 5. Don't really want to mess with the new windowing system and I can't put Wayland/Weston on a lot of my smaller projects. I'm pretty much locked into 4.8 (and it's eternally open tickets) for life.

witty_username 11y ago
> Wayland/Weston on a lot of my smaller projects Huh? Qt5 doesn't require Wayland; I've used it on X.
turrini 11y ago
Qt5 doesn't require Wayland, I'm using Qt 5.5.1 with widgets on embedded environments (X11 included) without problems.
- joezydeco 11y ago
  X11 included Yeah, um, not possible for me. I use the Linux framebuffer and that's it.
- deleted 11y ago
  [deleted]
turrini 11y ago
And it does support Linux FrameBuffer. http://doc.qt.io/qt-5/embedded-linux.html http://doc.qt.io/qt-5/embedded-linux.html
- ultramancool 11y ago
  The thing to note here is that the stripped out the windowing system implementation for embedded machines. So if you're using framebuffer without X11 or Wayland you're on your own for windowing now, which was previously provided in Qt4. That's my understanding at least, I don't use Qt on embedded platforms though, can anyone confirm this?
  - joezydeco 11y ago
    That's my understanding as well. I haven't looked deep enough into the QPA stuff to understand it.
  - slavik81 11y ago
    I don't work on embedded platforms, but it seems Qt5 supports directfb, which can do windowing. http://doc.qt.io/qt-5/embedded-linux.html http://doc.qt.io/qt-5/embedded-linux.html http://stackoverflow.com/a/21489384/331041 http://stackoverflow.com/a/21489384/331041

jabjoe 11y ago

Yes, MOC and QT's C+++ is really an awful thing. Copperspice being just normal C++ is interesting. Have to see what happens. But for me, C is where my heart is, so there is still two + that need to go for me. ;-)

rhodysurf 11y ago

Whoa thanks for pointing out copper spice! I use Qt everyday at work and this could be cool to mess around with for some projects.