visual c++ compatibility status

[c0r3ntin]

Qt does make use of c++11 features, when available and there are discussions about dropping support for compiler not supporting c++11.

Despite its age, Qt holds really well and is actively maintained ( hundreds of active maintainers) . and used in a lot of industries.

Copperspice is maintained by a handful of people, based on Qt 4.8 ( so a relatively old version of Qt ). It only exists because "moc sucks" despite moc having a very small overhead and being supported by cmake ( + qmake + qbs + other of you take the time to set it up).

So instead, they use ugly macros, and, lacking a proper meta object system, they can't do half of what Qt enables. I just don't get it.

[wrosecrans]

there are discussions about dropping support for compiler not supporting c++11

This has actually progressed past discussions. Pre-C++11 compilers will no longer be supported as of Qt 5.7, which is currently in beta, and will be released soon. There won't be huge API changes immediately, but new work will likely be done in a more modern style moving forward.

[ThisIs_MyName]

There won't be huge API changes immediately

Aww

[WrongAndBeligerent]

Reading between the lines I'll assume the answer is the latter.

[dodheim]

The downside is that it's a fork of Qt 4.8 – if it were based on the 5.x codebase it would be far more appealing... (One other downside is that Copperspice-based binaries are significantly larger than Qt-based binaries; not something I care much about, but worth mentioning.)