2 ms·
True to a point, but come on - one has to admit that Visual Studio, overall, is vastly easier to use to develop software as the equivalent typical Unix environm
by roel_v 16y ago
True to a point, but come on - one has to admit that Visual Studio, overall, is vastly easier to use to develop software as the equivalent typical Unix environment. Setting project dependencies (linking with other libraries), for example, is after 30 years still a topic that make me want to stab myself in the eyes every time I need to (again) look up how to change the makefile. That is, if they're using make, which sucks but which most people use. But if they're using, oh, scons, or a custom one like boost, well good luck making _any_ changes to that without spending hours just getting up to speed.
There may be some minor counterexamples, but overall, Visual Studio is a _vastly_ superior development experience (for C++) than any other environment.
- rbanffy 16y agoVisual Studio's "ease of use" may lead to developers who can't write a makefile (because they don't have to map dependencies), who don't really know (because they don't have to) what libraries the linker is linking the program against and who don't care if the build process is convoluted or fragile (when I had to develop in a team we had to standardize the full path - down to drive letter - we would put everything across all members of the team) because the IDE takes care of it (most of the time). I'll take the "you have to know what you are doing" route any day.
- roel_v 16y agoWhy 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.