I've been using Taskfile. Are just / mise much better?
Use Task Runners for Common Coding Tasks
21–30 of 33 posts
Re: Use Task Runners for Common Coding Tasks
#22It's really easy to learn - about an afternoon to peruse the docs. And quite capable.
Re: Use Task Runners for Common Coding Tasks
#23Re: Use Task Runners for Common Coding Tasks
#24I've been using Taskfile. Are just / mise much better?
I have been using just for some projects and really like it. I looked at mise to replace direnv in the few places I use it, but between mise trying to do so many things and the in terminal advertisement for a problematic company I want nothing to do with, I have halted all plans I had for learning more about mise.
Re: Use Task Runners for Common Coding Tasks
#25Re: Use Task Runners for Common Coding Tasks
#26just use just! It's really easy to learn - about an afternoon to peruse the docs. And quite capable.
Re: Use Task Runners for Common Coding Tasks
#27Earlier quoted context omitted.
I have been using just for some projects and really like it. I looked at mise to replace direnv in the few places I use it, but between mise trying to do so many things and the in terminal advertisement for a problematic company I want nothing to do with, I have halted all plans I had for learning more about mise.
What in terminal ads do you mean? I don’t recall ever seeing an ad of any kind in mise. Not saying you’re wrong, just that our experiences are different here.
Re: Use Task Runners for Common Coding Tasks
#28just use just! It's really easy to learn - about an afternoon to peruse the docs. And quite capable.
I migrated to mise from just. Mise handles more stuff (tool versions, environment vars) and also has nicer ergonomics for specifying tasks
Of course, if those aren't dynamics you have to deal with, definitely go with what works.
There's also invoke (https://www.pyinvoke.org/). I suspect it too is more powerful than just, and I know teams that use them.
Re: Use Task Runners for Common Coding Tasks
#29Earlier quoted context omitted.
I migrated to mise from just. Mise handles more stuff (tool versions, environment vars) and also has nicer ergonomics for specifying tasks
I'm not going to argue since I haven't used mise, but how beginner friendly is it? The nice thing about "just" is literally the "can learn in an afternoon". When I was in a team of, well, less motivated developers, that mattered. It meant they could modify and maintain the justfile without everything depending on me. Of course, if those aren't dynamics you have to deal with, definitely go with what works. There's als…
Re: Use Task Runners for Common Coding Tasks
#30Earlier quoted context omitted.
I'm not going to argue since I haven't used mise, but how beginner friendly is it? The nice thing about "just" is literally the "can learn in an afternoon". When I was in a team of, well, less motivated developers, that mattered. It meant they could modify and maintain the justfile without everything depending on me. Of course, if those aren't dynamics you have to deal with, definitely go with what works. There's als…
One issue with Just is that by default each line in a recipe is executed in a sub shell. Set a variable in line 1 and you can’t use it in line 2. Mise `run` blocks are embedded shell scripts. Alternatively, you can pull those scripts out into individual files so that you can edit them with syntax highlighting etc with any editor that understands shell scripts. Perhaps you can with just now, too, but mise makes it tri…
just supports the same. If you begin a recipe with a shebang (#!/bin/bash), then it dumps the whole recipe to a file and executes it as a shell script.
Not limited to bash - you can do the same with Python, etc.
As for scripts in their own files vs embedded in a justfile: I've noticed people's opinions vary. Even in my team we'd debate the issue. I prefer them in the justfile so I can read them in one place - as long as it's not huge. Some team members preferred them in their own files.