The depend mgmt part is like that because people have different wants. There are DevOps wants, system packager wants, user wants and coder wants. And they are s

The depend mgmt part is like that because people have different wants. There are DevOps wants, system packager wants, user wants and coder wants. And they are somewhat orthogonal, but not entirely. Each of the tools you mention have their good part wrt/ one of those four categories, and the rest is an afterthought. They did not end up doing one thing well, but one thing well and the other three too. Not as well. The way, or one way to change that would be to borrow the overall idea and semantics from each "good" implementation, but to limit it to just that; and build four separate projects under one community, so that there is pollination of knowledge and efforts, but no cross-contamination of goals and semantics. I'm not sure I am the person to start something like that.