3 ms·

> Since the justfile is a single file, you're not cluttering up your directory. You can do the same with any other scripting language, because with most popula

> Since the justfile is a single file, you're not cluttering up your directory. You can do the same with any other scripting language, because with most popular languages it's quite easy to handle cli-parameters on that level. And using a single messy file is usually not a good pattern. But on the other side, "just" comes with builtin tab completion which you would not get for any random script out-of-the-box. And if you are only using half oneliners or very short scripts, the messiness of a single file does not matter that much. Though, how well this will scale over time is a different topic.

dividedbyzero 4y ago
> And using a single messy file is usually not a good pattern. I find my Justfiles rarely ever get large enough to become messy, and then I just factor out the large tasks as scripts and it's all nice and tidy again. Almost all of my projects with a Dockerfile have docker-build and docker-run-local just tasks and those are pretty much always one-liners, and usually that's as complex as it gets. I treat Justfiles more like runnable readmes than a framework for homebrew build systems; if I need a proper build system, I'm probably going to invoke it via a one-liner in a just task.