3 ms·
My number one reason to use make is to have a single centralized location for project commands. If I see a Makefile at the root, I can quickly scan it and have
by 0cf8612b2e1e 3y ago
My number one reason to use make is to have a single centralized location for project commands. If I see a Makefile at the root, I can quickly scan it and have an overview of what high level actions I might execute.
Note that I have recently switched to Just (https://github.com/casey/just https://github.com/casey/just). While not technically the exact feature set as make, it covers all of the ground for what I typically do. It gets the benefit of history and discards a lot of make cruft to make a more predictable experience.
- jrm4 3y agoSo..dangit. The other thing I've been working on is a personal calendar todo list thing; after years of trying to use other peoples things, I realize I know just enough to make something that works with how I think and what I need (in short, a little like Linux Remind, but with the ability to mark things as done in a way, and the flexibility for "due" dates to go "stale" and still show up) Anyway, the units/items are individual files with content + some tags with dates. And I've been doing a thing where I source a file with a ton of functions. And..it looks like this is a better version of that. Wild. hmm.