| ▲ | Sl1mb0 a day ago |
| > dependency inclusion _should not_ be a main criterion for evaluating how good a build system is That's just like, your opinion, man. |
|
| ▲ | lutusp a day ago | parent | next [-] |
| > That's just like, your opinion, man. I would love to know how many younger readers recognize this classic movie reference. |
|
| ▲ | taminka a day ago | parent | prev [-] |
| i mean, unless you have some absolute divine truths, that's kind of the best i have :shrug |
| |
| ▲ | virtualritz a day ago | parent [-] | | There are no truths but your opinion in this case runs counter of what 35 years developing software have taught me. 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. | | |
| ▲ | taminka a day ago | parent [-] | | in my original comment i specifically mentioned that C (and C++) situation is also too extreme and not optimal... |
|
|
