[guitarbill]

[flagged]

[bsnnkv]

> I get that your project is Windows-only, but many projects aren't.

Nit: At this point you're better off starting a separate comment thread since you yourself already know that what you are about to talk about is not what my comment is talking about.

[guitarbill]

> Also has excellent Windows[1] support so I can take it everywhere!

Nit: You mentioned it can be used "everywhere". That would be a useful feature! But while it's kinda true, there's some quite big limitations IMO

[3eb7988a1663]

The shell can be configured per OS. So, Windows can be set to use PowerShell and Linuxy systems will use sh.

From the docs

  set windows-shell := ["powershell.exe", "-NoLogo", "-Command"]

  hello:
    Write-Host "Hello, world!"

Few things work seamlessly across platforms, and that does not seem like a huge burden.

[squeaky-clean]

> Wait, by "has excellent Windows support" you mean you have to set it to use Powershell or hope `sh` is installed on

I don't get what the problem is here? Do you protest against shebangs too? Why does a build script for a Windows only app need to use sh instead of powershell? I think you're interpreting "excellent windows support" to mean cross platform, and that's not what it means.

> So not only do you need just installed, which is yet another dependency,

Yeah if you want to use some software, your computer needs that software. That's not a dependency. So we're talking zero dependencies, or one of you absolutely need sh.

[burnished]

To be fair it is another dependency for the project that you are using just with. Its probably not software that you use for its own sake.

[BeetleB]

You can use the usual cmd (I do). You're not limited to Powershell. Also, you do understand that if a tool has first class support for Windows, that does mean it prioritizes Windows tools, right? Imagine I made a command runner, and said it has "excellent Linux support", and then someone comes along and complains that you have to install Powershell on Linux to use Windows recipes.

You can have Windows only recipes and Linux only recipes.

Furthermore, if you have bash installed on Windows (e.g. via git bash), you can put a shebang in your recipes to use bash.

We develop in Windows and deploy in Linux. Most of our recipes work in both OS's - either we use bash or Python for the recipe. The few that don't - we just mark as Windows only or Linux only so they're not available in the wrong OS.

> So not only do you need just installed, which is yet another dependency,

You do realize that Windows by default comes with almost no development tools, right? So yes, you do actually need to install things to get work done. The horror.

I'll also note that while you complain about just, you provide no alternative.

Weirdest rant ever.

[MatmaRex]

You can keep your commands simple enough so that they can be executed by both `sh` and `cmd.exe`. If you need anything more complex than invoking other programs, `&&`, `|` and `>`, it's time to rewrite your build script in a real programming language anyway.