It's like saying that a road bike is "bad" because it isn't as comfortable as your city bike. Different beasts for different needs.
It's like saying that a road bike is "bad" because it isn't as comfortable as your city bike. Different beasts for different needs.
Also because the laws of physics (and the math to do approximation) don't change very often. The older that Runge-Kutta function is in the codebase, the more chance it has to be part of the sample code that they test the compiler's optimizer/benchmark with too!
And Fortran is old enough it's possible to build wrappers around it, should the user really need a new interface.
Did you ask the users of the system or you just assume they don't want one?
The author is looking at it from an 'everything is an App' world, without the domain knowledge of Meteorology or HPC calculations. Implying that a lack of 'user interference' equalls 'bad software' is a very uninformed claim.
Equally misplaced outrage with trying to compare VSCode, from a company with 143 billion in revenue, with (often decade old) EHR systems which are decided 'on a budget' by Heads of clinical departments (AND Purchasing/Finance) with little to no input from actual 'end users'.
I'm pretty sure the "users" of the system are mostly programmers who write batch jobs.