the point isn’t to replace existing use. To take your analogy of cars, we aren’t retrofitting cars with new tech.
But maybe it means that new projects use a more accessible build system. I’m not saying Task is the answer, I’m just saying Make is an issue for a lot of reasons like accessibility and portability to multiple toolchains and systems.
If you’re just coding for yourself, it’s not important. Nobody is saying you should change. But if you’re coding for an ecosystem, it’s always worth evaluating where changes can be made and then evaluating case by case if the pros outweigh the cons.
Re:Taskfile: A Modern Alternative to Makefile
by Brian_K_White on Monday July 17, 2023 @09:10AM
(#36757837)
Accessible is merely an opinion not a fact or an argument backed by a fact.
Make is the definition of portable for that job, so that was a weird argument to try to make.
I see a consistent pattern of unfounded argument from someone who has nothing more than "old=bad" or "new=progress"
Make is easy for certain folks, yaml for others. If a project has been using make for years, should they be forced to replace it since someone believes they are gatekeeping? What happens if said project rejects a pull request that replaces said makefile with task file requiring python and yaml?
I'm pragmatic and also say if it gets the job done OK, but must I replace make with task if someone suggests I'm gatekeeping just because I have a pragmatic point of view?