3 ms·
> every thing you don't understand in your code or build system will eventually come back as increased cost I agree with this. But what has that got to do wit
by georgieporgie 16y ago
> every thing you don't understand in your code or build system will eventually come back as increased cost
I agree with this. But what has that got to do with Visual Studio and makefiles?
Is your point that Visual Studio is hard to use, somehow? I've created quite complex build systems using Visual Studio and scripting. I'll admit I've had rough patches where it's been hard to figure out where a setting might be, or where I forget to set things consistently (e.g. library inclusion across build targets), but it's pretty full-featured and reasonably easy to grasp. It strikes me as consistent, once you learn the basics.
Perhaps your point is that makefiles are easier to review "at a glance"? I don't really agree with that, since it depends entirely on one's competency with makefiles versus Visual Studio project/solution configuration.
I could be missing something entirely, though, so I welcome any additional take on it.
- rbanffy 16y agoI think the biggest point is that it's much harder to find a developer that understands the build mechanism of a project now than it was, say, by the mid-80's. We are doing more complex builds and VS makes it easy to fall prey to a huge pile of complexity where there should be a much smaller, addressable, tangle of dependencies. The point is that what appears to be an easy approach to project build management is, in fact, a loaded shotgun aimed at your feet.