Re:fabricate: The better "make". Finds dependencies automati...
by growt on Monday July 27, 2009 @06:10AM
(#725644)
I haven't tried fabricate yet, but I think the number of build-tools out there is a sure sign that something fundamental is broken.
[ Parent
| on HN ]
Re:fabricate: The better "make". Finds dependencies automati...
by tvon on Monday July 27, 2009 @06:13AM
(#725646)
I think it's just the nature of the beast, and an example of a complex problem with a lot of different solutions.
Re:fabricate: The better "make". Finds dependencies automati...
by modeless on Monday July 27, 2009 @12:49PM
(#726170)
What's broken is the C preprocess/compile/link process. C needs to get a modern module system and ditch the antiquated preprocessor and linker.
Re:fabricate: The better "make". Finds dependencies automati...
by kscaldef on Monday July 27, 2009 @12:10PM
(#726093)
I wouldn't claim it's the full story, but IMO part of what's fundamentally broken is the phenomenon of single-language programmers. This leads to the belief that your entire tool chain needs to be written in a single language. So now every language has it's own build tool (or 2, or 3), and god help you if you have a multi-language codebase and need to have a unified build system.
Re:fabricate: The better "make". Finds dependencies automati...
by sp332 on Monday July 27, 2009 @07:27AM
(#725684)
I think it's just down to the popularity of make. People who are starting new projects use make because "everybody's using it, it must be the best!" Then, when make becomes a pain in the butt, they write their own because they've already decided that there's nothing better out there.