Search Results

Documents authored by Rainer, Austen


Document
Technical Track Paper
What Do We Really Know About Fortran?

Authors: Austen Rainer, Andrew Brown, Rebecca Taylor, and Simon Hettrick

Published in: LIPIcs, Volume 394, 20th International Symposium on Empirical Software Engineering and Measurement (ESEM 2026)


Abstract
Background. Anecdotal evidence suggests that the Fortran ecosystem - the language, tooling, codebases and broad community - continues to make a significant international contribution to science and engineering. Yet the common perception appears to be that Fortran is old and obsolete and, as a result, one should divest from it. There is no empirical evidence - e.g., no contemporary or historical survey - to corroborate or contradict such perception. A consequence is that this perception may be not only mistaken but also damaging to the Fortran ecosystem and to the global contribution that the ecosystem continues to make to society, the economy and environment. Aims. To gather empirical evidence on the current state of the global Fortran ecosystem, in order to corroborate or challenge perceptions about the language, tooling, codebases and community. Method. We conduct an international survey of the Fortran community, collecting information from 150 respondents across 25 countries. Results. We report results about codebases (e.g. code size varies from 1KLOC to 5MLOC), community demographics (e.g., most respondents are male; most respondents hold doctorates), challenges (e.g., code complexity, human resource) and perceptions of Fortran (only 15% consider their codebases to be legacy codebases). Conclusions. Our results provide the first descriptive benchmark of the Fortran ecosystem which can act as a resource or reference for future research and practice. Also, our results suggest that Fortran may be better understood as a highly-valuable, niche, contemporary ecosystem, one which continues to contribute to world-leading research in many science and engineering disciplines. As an "edge case", it is ideally placed to provide unique and insightful contributions to our understanding of (scientific) software engineering, e.g., technical debt, refactoring, code complexity, and the significance of application domain knowledge. Since all codebases, regardless of language, have the potential to become legacy systems in the future, Fortran is actually at the forefront of confronting long-term challenges and consequences of engineering complex (scientific) software systems.

Cite as

Austen Rainer, Andrew Brown, Rebecca Taylor, and Simon Hettrick. What Do We Really Know About Fortran?. In 20th International Symposium on Empirical Software Engineering and Measurement (ESEM 2026). Leibniz International Proceedings in Informatics (LIPIcs), Volume 394, pp. 16:1-16:20, Schloss Dagstuhl – Leibniz-Zentrum für Informatik (2026)


Copy BibTex To Clipboard

@InProceedings{rainer_et_al:LIPIcs.ESEM.2026.16,
  author =	{Rainer, Austen and Brown, Andrew and Taylor, Rebecca and Hettrick, Simon},
  title =	{{What Do We Really Know About Fortran?}},
  booktitle =	{20th International Symposium on Empirical Software Engineering and Measurement (ESEM 2026)},
  pages =	{16:1--16:20},
  series =	{Leibniz International Proceedings in Informatics (LIPIcs)},
  ISBN =	{978-3-95977-450-5},
  ISSN =	{1868-8969},
  year =	{2026},
  volume =	{394},
  editor =	{Feldt, Robert and Paasivaara, Maria and Mendez, Daniel and Wagner, Stefan and Bar\'{o}n, Marvin Mu\~{n}oz},
  publisher =	{Schloss Dagstuhl -- Leibniz-Zentrum f{\"u}r Informatik},
  address =	{Dagstuhl, Germany},
  URL =		{https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.ESEM.2026.16},
  URN =		{urn:nbn:de:0030-drops-279847},
  doi =		{10.4230/LIPIcs.ESEM.2026.16},
  annote =	{Keywords: Fortran, demographics, software engineering, research software engineer, computational scientist, software sustainability}
}

Any Issues?
X

Feedback on the Current Page

CAPTCHA

Thanks for your feedback!

Feedback submitted to Dagstuhl Publishing

Could not send message

Please try again later or send an E-mail