Hacker News Reader

From my perspective, Just would be more useful if it had some ability to skip steps where the input hasn't changed.

Like maybe a Justfile's recipe could produce a "<task>.complete" kind of file, and could decide whether to re-run the task based on whether the task's inputs (or its dependencies' inputs).

Also if that sounds like a useful feature, consider using Make.

View on HN

> Also if that sounds like a useful feature, consider using Make

Just not having that feature is _the_ defining difference in design between the two. If just were to ever add that it would likely kill its appeal. Not having that is what keeps the logic of a just invocation simple and what keeps Justfiles from devolving into the mess that Makefiles tend to with entangled build targets.

Make solves that problem. The problem that I have is that all of the tools I use day to day do their own dependency tracking and re-run tracking. Say I want to deploy a dotnet app to a k8s cluster - none of helm, docker, dotnet build, dotnet test expose their dependency tracking in a way that is straightforward to use with make. The most straightforward way to do it is to just run the commands anyway, IME.

Reply on news.ycombinator.com