The only build system that might someday replace make (2010)

Re:The only build system that might someday replace make (2010) by theamk on Sunday November 24, 2019 @12:46AM (#21618651)

Segfaults, double-frees and buffer overflows are not C's fault. Any programmer using C deserves them. Right?

Happily, not eveyone thinks this way. That's why there is myriad of safe languages -- from Ruby to Rust -- which replaced C in many areas. Sure, C is still around, but many people prefer to give up some control for lots more safety.

The same logic applies to build systems. Sure, you can use "low-level" build system to hand-write gcc invocation in each project, but a bigger system makes your build files much safer.

[ Parent | on HN ]

Re:The only build system that might someday replace make (2010) by amiga_500 on Sunday November 24, 2019 @06:47AM (#21619815)

This has got nothing to do with my point of using a changing code base to compile against.

[ Parent | on HN ]

Re:The only build system that might someday replace make (2010) by kubanczyk on Wednesday November 27, 2019 @02:03PM (#21650877)

This has a lot to do with your point that "they deserve it" being not useful to improve things. How about we give that project a tool that just doesn't have this dangerous functionality?

[ Parent | on HN ]