> write non duplicated code ... Like how many string implementations are there across c code bases. In one of projects I needed foo::string that can share data

> write non duplicated code ... Like how many string implementations are there across c code bases. In one of projects I needed foo::string that can share data with foo::variant without copying the data each time. So foo::string was implemented as a COW string - smart pointer for foo::string_data. std::string simply does not work in such requirements. So I am not sure I understand how cargo will help in this case. Either Cargo source repository will contain implementations of any possible permutation of requirements of strings or people will just use standard std::string. The only feature that I need in C/C++ is unified ability to include libraries in code: #define PNG_APNG_REQUIRED #include source "libs/png/png-amalgamated.c" I am perfectly fine with downloading png.tar.gz manually and putting it in place where I need it. In any case decision to include library to a product requires quite a lot of reasonings and architectural investigations. For typical web front-end projects NPM or Cargo probably make sense. But for, say, NodeJs or Cargo itself they should not use any such automatic downloader.