12,138 karma · joined February 8, 2013
Many people don't trust that math.
Both have compatibly implemented the standard C++ auto. Since 2011 or so.
If you're engaging with it, it's for you.
1. General named module use: https://www.kitware.com/import-cmake-c20-modules/
2. Importing the std module: https://www.kitware.com/import-std-in-cmake-3-30/
Language ecosystems like Rust and Go, and even Haskell shrink the problem space to a smaller universe to grab dependencies. You can see this by how awkward it would be to build a program containing those three languages. They all have different package repositories and build workflows.
C, Fortran, C++ have very rough tools, but the community wants, and often needs, a wide range of dependency management options. Like mixing languages. Or shipping to PYPI. Or integrating with exotic embedded build environments.
Even for mixed drinks, the ABV can vary a lot more compared to lagers, pilsners, etc. The sugar content can be quite a bit higher in mixed drinks as well.
In particular, durable goods (and human bodies and even hair) need a lot of maintenance. So far, at least, robots aren't especially gifted at maintenance tasks.
But mostly, it's not realistic to directly wire up calls to g++ anymore outside of research examples. Note that other compiled languages use systems like gobuild, cargo, Maven, etc. instead of fiddling with gccgo, rustc, javac, etc. directly.
I think it's true given the goal to support a specific set of requirements of modern build systems.
The problem is that there is no separate dependency management protocol to target, and there is no separate projects description configuration format. That means build systems end up trying to interoperate with, or even implement large portions of, those kinds of subsystems.
The problem is that there are a variety of viewpoints on the distinction. Many of the viewpoints are contradictory or otherwise incompatible.
That's why I think the words are effectively ambiguous. I don't communicate in a way that assumes my audience members have a shared and coherent understanding of the distinction.
As an aside, to pick nits on Bernstein's definition of morality:
> Morality refers to right and wrong as a felt sense.
Many people wouldn't self-describe as having moralities that rely on "felt sense". They might even bristle that morality operates in some of the ways that food preferences do. In particular, a lot of moral systems have a notion of self-evident and universal truths. The Declaration of Independence prefaces itself from that perspective, for instance.
Though I also think Nix and Bazel are typically not the right starting points for most projects. If you're not committed to having at least four experts on those complex tools in perpetuity, find something simpler.
To be clear, inventing your own, better system is typically as bad. Language specific ecosystems can be too, but it's often hard to avoid both Maven and gradle if you're a Java shop, for instance.
Also, meson's build dependencies (muon, python) are a lot for some of these projects.
Also the basic workflows for the alternative build systems have maybe ten more characters to type. It's not bad.