I have seen few hells as bad as "just use the target runtime for build."
Re:Learn Makefiles with the Tastiest Examples
by jjnoakes on Thursday May 25, 2023 @07:14PM
(#36077665)
It can be done well though, and when it is, it removes friction from the development process.
Re:Learn Makefiles with the Tastiest Examples
by paulddraper on Monday May 15, 2023 @10:32PM
(#35957183)
Step 0: Ensure your project only uses one thing.
Re:Learn Makefiles with the Tastiest Examples
by alwillis on Tuesday May 16, 2023 @12:42AM
(#35957820)
> A project that's heavy JS? Use a JS task runner.
Trying to keep up with JS task runners for web projects is why I started using Make and haven’t looked back.
Re:Learn Makefiles with the Tastiest Examples
by jjnoakes on Thursday May 25, 2023 @07:13PM
(#36077656)
Sure but if a developer already has a JS runtime and they don't have Make installed, you've added unnecessary friction to the development process.
I hate JS as much as the next guy, but if I'm developing in JS, I use a JS task runner. Even a simple one. There's not much to "keep up with" IMO - they are quite easy to create and use, if the common/popular ones are missing features or move too fast for you.
At least, that's how I prefer to do it. A project that's heavy JS? Use a JS task runner. Heavy python? Python task runner. Heavy shell? And so on.