3 ms·
I do this too, my reasons are: * It's an old habit, I'm used to handwriting my own Makefiles for every project, and every time I start a new project it's an in
by gnulinux 6y ago
I do this too, my reasons are:
* It's an old habit, I'm used to handwriting my own Makefiles for every project, and every time I start a new project it's an instinct to create a .gitignore and Makefile
* There is always a possibility of needing make features in the future. Like nowadays my makefiles have `make build` recipe which builds docker containers via docker-compose and a `make run` that depends on `build` and then shells into that container.
* make is easier to use than shell scripts since you can just do `make <cmd>` to run your command