# An evaluation of risks associated with relying on Fortran for mission critical codes for the next 15 years

**URL:** <https://fortran-lang.discourse.group/t/an-evaluation-of-risks-associated-with-relying-on-fortran-for-mission-critical-codes-for-the-next-15-years/5644>\
**Category:** Uncategorized\
**Created:** [April 24, 2023, 10:22pm UTC](https://fortran-lang.discourse.group/t/an-evaluation-of-risks-associated-with-relying-on-fortran-for-mission-critical-codes-for-the-next-15-years/5644 "2023-04-24T22:22:43Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![shahmoradi](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/shahmoradi/32/3151_2.png) [@shahmoradi](https://fortran-lang.discourse.group/u/shahmoradi)\
**Post date:** [April 24, 2023, 11:54pm UTC](https://fortran-lang.discourse.group/t/an-evaluation-of-risks-associated-with-relying-on-fortran-for-mission-critical-codes-for-the-next-15-years/5644/3 "2023-04-24T23:54:30Z")

</div>

> This paper seems to project a feeling that we  
> have no control over the future of our  
> computing environment. LLNL specs systems  
> that are good for C++ and ignore Fortran,  
> because they made that switch twenty years  
> ago. The UK’s Archer2 system was spec’d to  
> run Fortran codes, because over 75% of their  
> cycles are Fortran. We could choose to invest  
> in computers and software environments that  
> are good for our codes and our mission. $10M  
> put towards getting [company name] to  
> improve their compiler is nothing compared  
> to the costs of replacing Fortran in our code  
> base.

---

_[View the full topic](https://fortran-lang.discourse.group/t/an-evaluation-of-risks-associated-with-relying-on-fortran-for-mission-critical-codes-for-the-next-15-years/5644)._