Hacker News new | past | comments | ask | show | jobs | submit login

Saying make is a solved problem is a real failure of imagination. I used to do a lot of work on Blaze and Bazel. I intend to add support for a lot of the things it does to GNU Make. Such as using ptrace() to make sure a build rule isn't touching any files that aren't declared as dependencies. I can't do that if our imagination is stuck in the 80's with all this DOS and Amiga code.



> Saying builds are a solved problem is a real failure of imagination.

Don't put words in my mouth, I said GNU make is a solved problem.


That sentence doesn't even make sense.


People can just use other tools like Bazel or Ninja.

Make works the way it’s intended to work. Leave it as is.


I wrote Bazel's system for downloading files. https://github.com/bazelbuild/bazel/commit/ed7ced0018dc5c5eb... So I'm sympathetic to your point of view. However some of us feel like people should stop reinventing Make and instead make Make better. That's what I'm doing. I'm adding ptrace() support. That's something I asked the Bazel folks to do for years but they felt it was a more important priority to have Bazel be a system for running other build systems like Make, embedded inside Bazel. So I asked myself, why don't we just use Make? It's what Google used to use for its mono repo for like ten years.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: