> A small drawback is that just isn’t readily available on developer’s machines (unlike bash and make)

Looking back, this was usually a substantial stumbling block for adoption of new tooling. Things have changed. All one has to do is look at what JS programmers will go through to scratch build entire toolchains on the back of npm. IMO, the bar has been moved up to allow _some_ installation friction rather than none.

IMO, if the tool is a solid improvement and installation is a one-liner, use it and promote it loudly so it continues to get support.