3 ms·
Why is all of this bad? (except from your example which I don't understand but which sounds not good) Division of labor, remember? Why should we force all of th
by roel_v 16y ago
Why is all of this bad? (except from your example which I don't understand but which sounds not good) Division of labor, remember? Why should we force all of this useless stuff onto each and every developer? If there is one guy on the team who knows how to fix issues with the project files and dependencies and whatever, the rest of the team can get on with their work instead of each and every one having to read man make every two weeks.
This attitude of "to drive a car well you have to be a mechanical engineer!" is dangerous to efficiency. As is the Stockholm syndrome that so many make users seem to be suffering from. The difference between the two is that with Visual Studio, you can defer learning about the build system in depth until the moment that you actually need it, whereas with make you need to spend a whole of time upfront, for no discernible gain. I'll take a 'easy things are easy, hard things possible' approach any day.