The containers according to [1] are array, vector, deque, forward_list, list, *set, *map, stack, queue and priority_queue. All of these are good general implementations that can and should be used for most C++ software.
Some classes of software require better performance or certain special guarantees and then it makes sense to consider specialized implementations.
Added up with "And when your project scales, Replace asyncio with uvloop, Coroutine with gevent, http.server with gunicorn and everything else with a cython based alternative".
Or personally I just say 'Use go instead' to someone who's just getting into programming for developing a project which could potentially scale.
This, of course, causes everyone to roll their own String, which is probably almost as bad.
So, now we have a zillion String libraries, all of which suck.
All because the C++ standard library doesn't provide a decent String.
If you look for example at other implementations like fbstring, the main benefit is performance.
However, Python's standard library is stuck with urllib, although these days they have the courtesy to tell any poor fool looking at the documentation that Requests exists, if you do use the standard library you get very primitive HTTPS handling, and so many wrong defaults.
Because these standard libraries have so many users, Hyrum's law means that you have to work very hard to fix anything.