dblotsky
Joined 13 years ago
Joined 13 years ago
I think the benefit of having one symbol exist in only one domain (e.g. “user_request” only showing up in the database-handling code, where it’s used 3 times, and not in the UI code, where it might’ve been used 30 times) reduces more cognitive load than is added by searching for 2 symbols instead of 1 common one.
[dancing] https://www.youtube.com/watch?v=fn3KWM1kuAw [cleaning clutter] https://www.youtube.com/watch?v=C8-w9eF24gU
1) I suspect GNU Make will be installed on any system where node code will run.
2) You don’t have to .PHONY anything that will never be a real file.
3) My bet is the Makefile will be shorter and clearer, but I am of course biased since I’m used to the syntax.
It kind of feels like the best trajectory is to start small with a general build system, and upgrade as needed? And then if you are confident the project will grow, starting with the specific build system fine too.
On that 30 minute note though: so, how big does the project need to be in order for Make not to be enough? And at that size, why wouldn’t the project invest the extra week it takes to get the Makefile correct?
So if one industry demands more labor, all others will feel the rising price of labor?
Real answer: probably, but a ton of production code is closed-source.
But why restrict to web apps? Most influential software projects in the world use Make.