Thanks for sharing the insight! As I observed when I was at Google: tcmalloc wasn't a dedicated team but a project driven by server performance optimization en

Thanks for sharing the insight! As I observed when I was at Google: tcmalloc wasn't a dedicated team but a project driven by server performance optimization engineers aiming to improve performance of important internal servers. Extracting it to github.com/google/tcmalloc was complex due to intricate dependencies (https://abseil.io/blog/20200212-tcmalloc https://abseil.io/blog/20200212-tcmalloc ). As internal performance priorities demanded more focus, less time was available for maintaining the CMake build system. Maintaining the repo could at best be described as a community contribution activity. > Meta’s needs stopped aligning well with those of external uses some time ago, and they are better off doing their own thing. I think Google's diverged from the external uses even long ago:) (For a long time google3 and gperftools's tcmalloc implementations were so different.)