3 ms·
Sometimes you actually do need to rewrite the whole project in a new language. FORTRAN just isn't the tool for the job anymore. But you'd still benefit a good d
by ToValueFunfetti 2y ago
Sometimes you actually do need to rewrite the whole project in a new language. FORTRAN just isn't the tool for the job anymore. But you'd still benefit a good deal from being highly suspicious that any person suggesting that course of action is naive to how much time and suffering it will entail.
Arguably, the American revolution wasn't even necessary. A lot of people died as a result. England would have potentially ended slavery decades earlier if the US was still a colony. Canada and Australia wound up in roughly the same spot without a revolution (though possibly as a second order effect of the American revolution).
- pklausler 2y agoWhy is modern Fortran no longer the right tool for a job?
- bumby 2y ago>FORTRAN just isn't the tool for the job anymore. This underscores the problem with generalities. I know of some applications that would be considered high-speed (both literally and figuratively, since they are related to rocket testing) that still rely on FORTRAN. So I think your statement needs some qualifies (what kinds of jobs?)
- ToValueFunfetti 2y agoI guess I should have put quotes around that. It was intended as a specific example of when that decision might make sense; you're using the wrong language for the job because it was the best choice when you started the project decades ago. I didn't mean to suggest that FORTRAN is not the tool for any job.