casey/just

…ree 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 world so in the process of the port I thought "I don't have to make posix calls, I can put it in sandbox and li…

I've found https://github.com/casey/just to be very very useful. Allows to bind common commands simple smaller commands that can be easily referenced. Good for humans too.

…son, 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.json, as long as…

1. https://github.com/junegunn/fzf for fuzzy search. Great for easily searching and selecting git branches + tags + commits, commands from shell history, files, shell jobs, processes, etc. 2. https://github.com/casey/just for more structured scripting.

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

https://github.com/casey/just is an uncursed make (for task running purposes - it's not a general build system)

…`. 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 could be a command alias or something, I probably am overengineering that lol. [0]: https://github.com/casey/just

If someone is interested in pursuing this approach further, there exist a polyglot task runner named 'just' [1]. [1] https://github.com/casey/just?tab=readme-ov-file#shebang-recipes

Just is better choice imho https://github.com/casey/just

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/main/make/APKBUILD And vim https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/community/vim/APKBUILD?ref_type=heads ### Downloading the internet to build a smallish software is always bad in my opinion.