Earlier quoted context omitted.
I could not agree more with every word you have written here. I would like to add that scientists are neither averse to change, nor too lazy to learn new tools. However, they typically only care about the solution to their problem, not about programming in general. It is thus futile to try to convince them to use a different tool from a programmers' point of view--you need to convince them by showing them how much si…
The thing is it isn't just about solving their problems. The tough thing is to convince them how much it would help the community as a whole. I have tried many times to download some PhDs code and attempt to get it to compile. Usually it can be done after a lot of effort and tweaking. But it would be beneficial for science if code was treated as important as the paper itself.
One could argue that it isn't. In science, the concept is usually more important than the implementation.
But I totally agree. Scientific code tends to be awful and I wish I knew what to do about that.