▲ | motorest 5 hours ago | |||||||||||||||||||
> Interacting with CLI tools using only env vars as arguments is cartoonishly bad dev experience. Make excels at what it's design to do: specify a configurable DAG of tasks that generate artifacts, execute them, and automatically determine which subgraph requires updates and which can be skipped by reusing their artifacts. I wonder: which tool do you believe does this better than Make? | ||||||||||||||||||||
▲ | system33- 4 hours ago | parent [-] | |||||||||||||||||||
Tup. https://gittup.org/tup/ https://gittup.org/tup/make_vs_tup.html But the Internet’s make mind-share means you still have to know make. Edit: and make lets you use make to essentially run scripts/utils. People love to abuse make for that. Can’t do that with tup. | ||||||||||||||||||||
|