HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
casey
just
Rust2016–2026
casey / just

just

🤖 Just a command runner

Command Line
Explore on GitHubRead Hacker News discussions
120Distinct people
152Mentions
4Explicit recommenders
36.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

🤖 Just a command runner

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Reminds me of `just`. I love `just`. (Although I've never used make...) https://github.com/casey/just

arcanemachiner used a recommendation phrase. 4 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year152 dated mentions

Observed mentions: 2016-11-10 08:57:09 UTC to 2026-10-21 13:45:06 UTC.

0102030402016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 9 mentions; 3 submissions, 6 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 10 mentions; 3 submissions, 7 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 24 mentions; 6 submissions, 18 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 39 mentions; 1 submissions, 38 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 30 mentions; 2 submissions, 28 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 20 mentions; 3 submissions, 17 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC110
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC514
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC936
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1037
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC24618
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC39138
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC30228
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC20317
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC11110

What Hacker News says

152 sources
skydhash·Oct 21, 2026
This is the dependency list of the just command runner https://github.com/casey/just/blob/master/Cargo.lock And the helix editor https://github.com/helix-editor/helix/blob/master/Cargo.lock Compare them to the dependencies of gnu make (pretty sure it’s only posix) https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/m... And vim https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/c... ### Downloading the internet to build a smallish software is always bad in my opinion.
In Security advisory: Critical remote code execution vulnerabilities, update now
grayrest·Aug 20, 2026
> Do you mean isolating build scripts by using a VFS mapped to the real FS and masking away everything the build script should not have access to? Yes. Essentially the idea was to find the source control root (or something configurable) and mount the real subtree into a VFS where everything interacts with the filesystem through the VFS. I can run wasm compiled versions of apps I don't really trust or run native patched versions that I do. For background, I'm writing a UI platform in Roc [1] and using just [2] in order to script things. I had extra tokens so I decided to do an LLM port of just over to Roc to exercise the compiler (it's pre-0.1, pushing the compiler leads to crashes) and people won't have to install Rust to write apps. Like wasm, Roc code can't access the outside world without the host providing the access to the outside wo
Read the rest
rld so in the process of the port I thought "I don't have to make posix calls, I can put it in sandbox and lie about it" so that's how I got here. I'm fairly close to being able to do hermetic builds so that's a possibility but this is mostly an exploration of whether the idea works or not. [1] https://roc-lang.org/ [2] https://github.com/casey/just
In Show HN: Kandelo – a POSIX-compatible multi-process WASM kernel for the browser
BeetleB·Jul 10, 2026
I can somewhat sympathize - I guess the debatable aspect is to what extent should you teach? If someone knows no development tools, then yes, it is good if someone in the team knows Visual Studio Code and can guide them. In my previous job, another senior person knew it and helped out (VSCode was not mandated, and they were free to use some other tool). I tend to focus on training people on the concepts (code navigation, debugging, version control, etc), and tell them that they're free to use whatever tool they like, but it's on them to learn how to use those tools to apply those concepts. I usually recommend VSCode and tell them there are plenty of videos/sites that explain them. Then if I see them doing something very inefficiently, I do a quick Google search to see if the more efficient approach is supported in their tool and send them
Read the rest
a link. It's important to hire people who can learn on their own (with guidance on what to learn). > For example, if I'm teaching a new hire to set up their vscode it is not very helpful to tell them "now you need to activate the python venv". It is much more helpful to be able to tell them "Now we're going to activate the python venv. To do that, open your command palette and search for 'select python interpreter'". Inspired by a submission some years ago on HN, I came up with a different approach in my last job. Everything the team did (including onboarding), had to be done via a just[1] recipe. No longer did we rely on outdated docs. just recipes, by definition, cannot be outdated because then we wouldn't be able to do our work. For onboarding, we had recipes that automated as much of the configuration as possible. For things that required manual work, the recipe would print instructions, and prompt the user to press Enter when they had completed the task. Sure, onboarding stuff can go stale as people don't onboard often, but we had a policy that if any senior team member had to help a newbie because the recipe was broken, then the senior member needed to fix the recipe and check it in. I left the job, but I still talk to some of the folks there. They still love the recipes. [1] https://github.com/casey/just
In In Emacs, everything looks like a service
rodarmor·Jun 16, 2026Submission

Ten Years of Just (and Lists)

I made my first commit to `just`, a command-runner written in Rust, ten years ago with the auspicious commit message "Initial commit. Broken." Thanks to everyone that has used `just` over the years, the authors of the huge variety of useful crates that `just` uses as dependencies. I'm especially grateful to all the feedback, design help, and issue reports I've gotten. `just` is largely a solo project, and my own use of `just` is fairly simple, so I rely on users to let me know what they're doing, what they want to do, and what works and what doesn't. I just (lmao, never gets old) released 1.53.0, https://github.com/casey/just/releases/tag/1.53.0, which has a huge new feature: lists! There have been many issues over the years which are hard or difficult to solve with strings alone, so now, instead of all values being strings, all values ar
Read the rest
e lists of strings. This preserves the simplicity of `just`'s single-type type system, what were strings are now lists of length one. This is an odd but hopefully pragmatic choice, and one shared by the rc and fish shells. Two headline features this enables are properly quoting variadic arguments: set unstable set lists foo *args: echo {{ quote(args) }} And mapping variadic arguments to dependencies, especially in parallel: set unstable set lists # call `compile` with each element of `args` in parallel [parallel] build *args: *(compile *args) compile target: But there is a a ton of functionality, all documented in the lists section of the readme, https://github.com/casey/just#lists, to avail yourself of. Thank you for using `just`, and do try out lists and let me know what you think!
5 points · Open discussion
axegon_·Apr 3, 2026
I used to do that but there are a few catches. As much as I brush off people who use any OS other than Linux, there is a time when you will have to do something on another operating system. A lesson I learned the hard way: Make on Windows sucks royally. While I agree with the general idea and I also tend to be conservative about new technologies (even more so with all the slop-coding lately), just[1] is now a very mature and well thought out alternative. [1] https://github.com/casey/just
In Show HN: Home Maker: Declare Your Dev Tools in a Makefile
embedding-shape·Jan 28, 2026
> My monorepos have become increasingly multilingual over the years, often due to dependencies, and it's not uncommon to find a make file, cargo.toml, package.json, deno.json, venv + requirements.json, etc. all living in the same root. Same! Usual move used to put everything in Makefile, but after getting traumatized time and time again from ever-growing complexity, I've started to embrace Just (https://github.com/casey/just) which is basically just a simpler Make. I tend to work across teams a lot, and make/just seems easier for people to spot at a glance, than scripts inside of a package.json that mostly frontend/JavaScript/TypeScript people understand to take a look at. But in the end I think it matters less specifically what you use, as long as you have one entrypoint that collects everything, could be a Makefile, Justfile or package.
Read the rest
json, as long as everything gets under the same thing. Could be a .sh for all I care :)
In Make.ts
embeng4096·Oct 29, 2025
Would creating a `main.py` with the dependencies installed either as a uv project or inline work for you? One thing I did recently was create a one-off script with functions to exercise a piece of equipment connected to the PC via USB, and pass that to my coworkers. I created a `main.py` and uv add'ed the library. Then when I wanted to use the script in the REPL, I just did `uv run python -i main.py`. This let me just call functions I defined in there, like `set_led_on_equipment(led='green', on=True)` directly in the REPL, rather than having to modify the script body and re-run it every time. Edit: another idea that I just had is to use just[0] and modify your justfile accordingly, e.g. `just pything` and in your justfile, `pything` target is actually `uv run --with x,y,z ipython` Edit edit: I guess the above doesn't even require just, it
Read the rest
could be a command alias or something, I probably am overengineering that lol. [0]: https://github.com/casey/just
In Uv is the best thing to happen to the Python ecosystem in a decade

Showing the 15 most recent of 152 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.