5 ms·
I'm not GP but: Make gives me a single, predictable and stable interface to the repo. From the root of the repo, I can type `make <tab>` and get a list of ava
by cassianoleal 2y ago
I'm not GP but:
Make gives me a single, predictable and stable interface to the repo.
From the root of the repo, I can type `make <tab>` and get a list of available tasks. Alternatively, there's a Makefile on the root.
With scripts, I need to type... what? `./<tab>` and look for clues? Maybe the scripts are in `scripts/`, maybe they're in `build/`, maybe they're in `ci/`...
Even if I know where the scripts are, `make task` is quicker and easier to type than `./scripts/task.sh`.
One could just use a make task to call a script, which I have done, but in most cases if you do that, what's the point of the script?
- chuckadams 2y ago> what's the point of the script? For starters, not having to indent every line with a tab, put backslashes at the end of each line, or double every $ sigil in the script. Being able to transparently replace it with perl or python or some other non-shell-script is an occasional bonus.
- cassianoleal 2y agoYou picked the least important point I made, stripped it out of context and argued against it. This is a strawman. Feel free to use it as a piñata, I don't care.
- deleted 2y ago[deleted]
- fuzztester 2y agohttps://news.ycombinator.com/item?id=40350681 https://news.ycombinator.com/item?id=40350681