Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Given these examples of a Justfile, it doesn’t seem worth this effort versus using a Makefile and not needing a compilation step (assuming Make is available everywhere). Does anyone have a Justfile example complex enough to demonstrate a significant advantage over Makefile?


I can offer this (warning, crufty real-world scripts ahead!): these make files and bash script (https://github.com/simonmichael/hledger/blob/137d825/Makefil..., https://github.com/simonmichael/hledger/blob/137d825/Makefil..., https://github.com/simonmichael/hledger/blob/a3c300b/bake) were replaced by this roughly equivalent Justfile (https://github.com/simonmichael/hledger/blob/137d825/Justfil...) (some old things were commented out, some new things were added).

I'm only a few weeks in, and just has its own learning curve, but I'm very pleased overall. Cognitive load is down, usability is up, robustness is up. ("After many years with make and plain shell ... for scripting, just is better enough, and the goal of clean consolidated efficient project automation is so valuable, that I am relying on it even though it's not installed by default.")


Just is fundamentally less capable but by extension less complex, and that’s by design. It’s essentially a way to group your shell scripts for a given project. It’s somewhat similar to make in terms of syntax but it doesn’t do anything make does like tracking whether a task needs to be rerun


why use make over sh/bash?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: