We've been using Taskfile, which is fantastic and super understandable, but it's only a task-runner and as such wouldn't meet OP's needs. I hated `just` and did not find it at all intuitive.

Only problem I have with the article is saying that Ruby doesn't work on Windows is just categorically false. It's one of the easiest languages to install and use on Windows, even easier than C# and Java, and I'm a Java/Kotlin dev, so that's saying something. It's literally just a single exe/msi installer.

But you wouldn't want to be using Rake anyway, it's not really that good, and is only useful if you're working in an environment where you don't want to install anything and you hate Make. Then Ruby is very often installed by default with Rake and so you get a 'free' build tool. Rake was good 10 years ago, but not so much anymore.

Anyway, if you needed a specific kind of tool and built it then all the power to you. Can't blame you for not wanting to use the other options!

> It's literally just a single exe/msi installer.

And so is .NET. Just install SDK from a single exe (or, on macOS, do 'brew install dotnet'), open VSCode, maybe get the C# extension. That's it. dotnet run, dotnet build, etc.

For scripting, there is 'dotnet fsi' for F# interactive. And you can also compile F# scripts directly into native executables with community tooling if you wish to make them full standalone programs.

What in particular tips the balance to Taskfile compared to just(file)? With one of my clients I’ve been using just for months, so I’m curious. Thanks!