>Sure, c/c++ has more libs, ... My problem is honestly that Cargo has spoiled me. C (& C++) may indeed have more libraries; but adding them to a project is a n

>Sure, c/c++ has more libs, ... My problem is honestly that Cargo has spoiled me. C (& C++) may indeed have more libraries; but adding them to a project is a non-trivial exercise. Assuming your project subscribes to the "build it with one command" philosophy then: - You'll need to install the target project's build system - You'll need to invoke that from your project's build system - You'll need to copy those artifacts (which depends upon implementation details of their build system) to the right output directory (which depends upon implementation details of your build system.) - Then finally you get to include the headers complete with ifndef guards. (Honestly it's getting increasingly more difficult for me to even tolerate C/C++ header files.) - P.S: probably repeat this list for every target platform you build on. --- When installing a package takes a single line of configuration, or a single command, I am far more likely to ignore my "not invented here shoulder-demon" and just add a 3rd party dependency. In C/C++ I actively avoid adding dependencies, regardless of how numerous they may be.