Given that I am writing a graphical application with Qt, it makes sense to go with Qt Concurrent
I would say this is not so simple. I personally would use the standard library as far as I can. However, there are limitations to consider:
Do you need to support your software on platforms that do not support at least C ++ 11?
If the question is yes, then using Qt solutions is the best option in Qt-based software. Even so, you may have different Qt solutions depending on your needs. One of the KDE weavers, but let's not go that far ...
Another question you could ask yourself:
Do you already have an existing code base, where is it used everywhere?
Depending on the answer, this can also provide an additional aspect of the solution, whether you prefer consistency or advanced thinking.
This also raises another question:
How much QtConcurrent do I need?
Depending on the exact answer, this may or may not be the best alternative. Please note that not all QtConcurrent functionality is in the standard library just yet, for example, something like QFutureWatcher with the Qt signal slot mechanism.
So, yes, as a Qt user, I would suggest using the standard library as much as possible. These days Qt even clearly depends on them, so it wonβt work on a platform that does not support it. In addition, the general direction seems to be similar to this in the Qt project itself. For example, a QtAlgorithms been deprecated in QtAlgorithms , but this is only one of them.