Yeah, and I believe they also did it with some other constructs like
std::unique_ptr. Not a fan of extremely thin JUCE wrappers around
std:: objects since their addition in C++11, but as has been said the JUCE APIs are much nicer to read than the
std:: ones and there is plenty of legacy code out there that uses it.
There are also certain cases like the JUCE
String class where the functionality, usability, and performance are massively improved over their
std:: equivalents and will likely never go away.
juce_core_legacy (or similarly named) module for JUCE constructs from the pre-C++11 era. This would also encourage users to adopt the