3 ms·
Why not just use make? I am constantly confused by people reinventing the wheel with new syntax and little benefit
by darby_nine 2y ago
Why not just use make? I am constantly confused by people reinventing the wheel with new syntax and little benefit
- eloisant 2y agoBecause make is a huge PITA
- maccard 2y agoWhen step one of using a tool is to disable the tools primary benefit (everything is phone) you’re reaching for the wrong tool. Like it or lump it, make deploy is much neater than docker build -t foo . && docker tag foo $item && docker login && docker push && helm apply I wish there was a flag for make which set it to be a command runner by default for the current makefile.
- darby_nine 2y agoMake's clear benefit is laying out a process as a series of dependencies.
- deepsun 2y agoWhy not just use shell scripts? Why additional complexity?
- darby_nine 2y agoShell scripts are additional complexity? I'm not sure what you mean. Adding structure reduces complexity.
- deepsun 2y agoNo I mean Makefiles, how author uses them, are additional complexity over shell scripts. The whole difference of Makefiles, their original idea was to not re-compile a target _file_ if it's already there. So if you need .PHONY -- you're using Makefiles wrongly.
- xigoi 2y agoBecause they have different purposes. make is a build system, just is a command runner.
- darby_nine 2y agoWhat's the distinction? What do just do better than make?
- xigoi 2y agohttps://github.com/casey/just?tab=readme-ov-file#what-are-the-idiosyncrasies-of-make-that-just-avoids https://github.com/casey/just?tab=readme-ov-file#what-are-th...
- kaba0 2y agoMake is hardly a build system
- mldbk 2y agoHonestly, it is because make is not written in Rust ;-) This is a sect and global trend to reinvent and re-implement the wheel with the Rust :D