like the entire point of my comment is that people have misguided criteria for evaluating build systems, and your comment seems to just affirm this?
That's just like, your opinion, man.
Obviously, I may be an outlier. Some crank who's just smitten by the proposal of spending his time writing code instead of trying to get a dependency (and its sub-dependencies and their sub-dependencies) to build at all (e.g. C/C++) or to have the right version that works with ALL the code that depends on it (e.g. Python).
I.e. I use cargo foremost (by a large margin) for that reason.
I would love to know how many younger readers recognize this classic movie reference.
I think dev_l1x_be's comment is meant to imply that your believe about people having misguided criteria [for evaluation build systems] is itself misguided, and that your favored approach [that the difficulty of including a dependency should be proportional to the risk you're taking on] is also misguided.