Convergence in the pip and conda worlds?

I think that the things conda "blames" pip for, are the same things that HPC cluster administrators blame conda for, if you replace "conda" by "system", i.e.

* don’t vendor things available as <conda=>system> packages
* do include additional dependencies for those things
* link against the import libraries/headers/options used for the matching <conda=>system> builds of dependencies

On cluster environments, we actually ask our users to *not* use conda, in large part due to these reasons.
https://docs.alliancecan.ca/wiki/Anaconda/en

conda is more like yum/apt than it is like pip, and that does not play well on a cluster, but our users keep coming to us wanting to use conda instead of pip (and then we show them that pip works better on clusters).