> This is the way. Shell makes for a terrible scripting language, that I start regretting choosing usually around the time I have to introduce the first `if` into my "simple" scripts, or have to do some more complex string manipulation.

I suppose it can be nice if you are already in a JS environment, but wouldn't the author's need be met by just putting their shell commands into a .sh file? This way is more than a little over-engineered with little benefit in return for that extra engineering.

The reasons (provided by the author) for creating a Make.ts file is completely met by popping your commands into a .sh file.

With the added advantage that I don't need to care about what else needs to be installed on the build system when I check out a project.

I just don't see the advantages.

▲

dsherret 2 hours ago | parent [-]

The benefit is you can easily scale the complexity of the file. An .sh file is great for simple commands, but with a .ts file with Deno you can pull in a complex dependency with one line and write logic more succinctly.

	▲	lelanthran an hour ago \| parent [-]
		> The benefit is you can easily scale the complexity of the file. An .sh file is great for simple commands, but with a .ts file with Deno you can pull in a complex dependency with one line and write logic more succinctly. The use-case, as per the author's stated requirements, was to do away with pressing up arrow or searching history. Exactly what benefit does Make.ts provide over Make.sh in this use-case? I mean, I didn't choose what the use-case it, the author did, and according to the use-case chosen by him, this is horrible over-engineered, horribly inefficient, much more fragile, etc.