>Why Fortran is a scientific powerhouse This is by design. I don't know how Fortran is any more, I didn't get as far as Fortran 77 since it wasn't 1977 yet.

>Why Fortran is a scientific powerhouse This is by design. I don't know how Fortran is any more, I didn't get as far as Fortran 77 since it wasn't 1977 yet. But students seemed to hate the old Format statements to get your printouts with. Properly done, a few lines of code could output reams of concise tabular data, but you had to be careful you didn't print out reams of gibberish instead. Those mainframe printers could chew through kilos of paper. OTOH, for a single page report, a customized printout of meaningful consolidated, summarized data, it could basically take up a whole page of Format statements and even more print statements in the code. A *whole* page. And there was no such thing as What-You-See-Is-What-You-Get for printing, it was what you expect is what you hope to get. Now it's the modern day in the chem lab, and with 10GB of modern scientific software on top of Windows, which requires a high-end desktop for this, I have not stopped wanting to print. And my data is cloud-ready like never before. But I have no use for that. After my data has lived a full life, it will go to heaven by itself. Seems like it could also expose my data to hell. What about my printout? "Low-code" derivative of Microsoft's Report Definition Language. You've got a template and a GUI and you can even move blocks around. What you see is even less of what you get. There are two main features not shared by Fortran: 1. You will *always* need some kind of iteration before you arrive at your final page format. 2. The code generated is *pages and pages* of XML to get a single printed page. If I had something as performant as Fortran Format statements it sure would have saved a lot of time.