3 ms·
> If anything, the fact that it's decades old and used in every major software project is a testament to its effectiveness, not a drawback. Part of the reason
by jjrh 9y ago
> If anything, the fact that it's decades old and used in every major software project is a testament to its effectiveness, not a drawback.
Part of the reason is because people see the superficial issues (like the discussion regarding spaces) before they see the value of years (or decades) of work. It doesn't help that when folks bring this up many times you get "you're holding it wrong" type responses.
I sympathise with both sides of the argument. I don't know the solution but it's unfortunate seeing folks reinventing the wheel and struggling with problems solved in the past.
- dblotsky 9y agoI definitely think Gulp and Webpack have a place. Where you have to write a Makefile fresh every time for every type of project, Gulp and Webpack come prepared with JS-specific stuff. That's perfect for a throwaway project or a small codebase where build performance and maintenance really don't matter. My issue is that people who need serious solutions forgo Make because "tabs, man", or because Webpack has pretty console output.