EASTL mostly doesn't have this problem because it as far as possible is a compliant implementation of the STL with a few specific extensions, mostly around memory management. It's not a library that provides STL-like functionality with a different API. Much of the custom allocator stuff has finally now been superseded with polymorphic allocators in C++17.
Source: former maintainer of EASTL (not the original author).
Comments
EASTL mostly doesn't have this problem because it as far as possible is a compliant implementation of the STL with a few specific extensions, mostly around memory management. It's not a library that provides STL-like functionality with a different API. Much of the custom allocator stuff has finally now been superseded with polymorphic allocators in C++17.
Source: former maintainer of EASTL (not the original author).
I would imagine that being a larger organization, there are dedicated resources for at least some documentation/POC's for questions/changes/etc.
The smaller the company, the less resources you have to maintain, the more issues you're going to run into.