[vimax]

Your shell file with a switch isn't going to do incremental parallel builds.

If you understand make, your makefile will behave as you expect it to. If you try to read a makefile as a shell script you'll constantly be surprised.

[Arch-TK]

The people this tool is aimed for don't use make to do incremental parallel builds. They use it to as a glorified shell wrapper which produces sub commands. That's what the use-case for this tool seems to be at least.

I know what make is and I know how to use it, thanks.

[wurosh]

And you have concluded this how? Again, in what way is this arcane power of make that you describe subdued by this tool?

[Arch-TK]

I've concluded this buy looking at some of the makefiles that people are referring to and the way the description of the tool is worded.

Calling makefiles a "single source of truth" for "dev commands" sounds to me like a glorified shell script aggregator. That's not what make is.

All in all I have two issues:

1. The naming of this tool. It's not make specific, you could literally make this tool run anything else and it would still work identically. But in this case it seems to be encouraging misuses of make.

2. The concept described by the tool's documentation that makefiles are "a single source of truth for dev commands".