The things make got right (and how to make it better)
blog.jgc.org
blog.jgc.org
file "target" => %w(prereq1 prereq2 prereq3 prereq4) |t|
sh "update", t.name, *t.prerequisites
end
Now, call me crazy, but I actually prefer "t.prerequisites" over "$^".If I were writing makefiles all the time, perhaps I'd appreciate Make's concise but obscure syntax. But maintaining makefiles takes only a small proportion of my time, and more syntax I have to learn, the more trouble I'm going to have remembering it.
Rakefiles are written in Ruby, a language I already use for development. The additional syntax I need to remember to use Rake is therefore very small. It's also a heck of a lot easier to work with Rake if you happen to want to do something a little complex or unusual!
Admittedly the syntax is /unique/ to makefiles, which I think is the biggest downside. There is a huge benefit to not having to learn one more way of doing things. And I think that's the big appeal of tools like rake (as well as the ability to easily leverage, libraries, and other higher order programming concepts). But for the simple tasks of compilation, and minor project management. Give me Make.
Who is swalling the snake oil?
All the build systems he was thinking of are not even worth criticizing, including make.
Check out Vesta, created about 25 years ago...
make is a complete mess. Trying to put lipstick on it and dress it in a champagne gown doesn't change the fact you got stuck with the ugly girl for the prom.
Your ideas on how to make it better seem produced by having your head down typing away at the monitor, rather than seeing the big picture.
Read a visionary system like Vesta. Then re-write this article, and forget about Make.