# It's 2025! Why Does Fortran continue to Dominate Weather and Climate Research?

**URL:** <https://fortran-lang.discourse.group/t/its-2025-why-does-fortran-continue-to-dominate-weather-and-climate-research/10378>\
**Category:** Advocacy\
**Created:** [September 2, 2025, 7:41am UTC](https://fortran-lang.discourse.group/t/its-2025-why-does-fortran-continue-to-dominate-weather-and-climate-research/10378 "2025-09-02T07:41:02Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carltoffel](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/carltoffel/32/1680_2.png) [@Carltoffel](https://fortran-lang.discourse.group/u/Carltoffel)\
**Post date:** [September 2, 2025, 7:41am UTC](https://fortran-lang.discourse.group/t/its-2025-why-does-fortran-continue-to-dominate-weather-and-climate-research/10378/1 "2025-09-02T07:41:02Z")

</div>

My boss sent me an article which might be interesting for you.  
It cites four discussions from here.

I couldn’t find the author, so he might be a silent reader.  
**Julius Uy** , if you see this, we’d be delighted if you joined the discussions here. Your perspective would be very welcome!

The article was posted on [Linkedin](https://www.linkedin.com/pulse/its-2025-why-does-fortran-continue-dominate-weather-climate-julius-uy-9fffc) and [Medium](https://medium.com/@julius.uy/fortran-in-weather-and-climate-research-migration-challenges-costs-and-strategic-decisions-66c985bae4a2)

> **[It's 2025! Why Does Fortran continue to Dominate Weather and Climate Research?](https://www.linkedin.com/pulse/its-2025-why-does-fortran-continue-dominate-weather-climate-julius-uy-9fffc)**
>
> The weather and climate research community has always faced a decision point regarding the continued use of Fortran versus migration to modern programming languages like Python. Based on a comprehensive analysis of current usage patterns, technical...

> **[Fortran in Weather and Climate Research: Migration Challenges, Costs, and...](https://medium.com/@julius.uy/fortran-in-weather-and-climate-research-migration-challenges-costs-and-strategic-decisions-66c985bae4a2)**
>
> The weather and climate research community has always faced a decision point regarding the continued use of Fortran versus migration to…

_IMHO the Medium article is more visually appealing, but there are no comments yet. However, the reading time on Linkedin is somehow shorter. 😂_

---

<div class="post-metadata">

**Author:** ![certik](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/certik/32/4_2.png) [@certik](https://fortran-lang.discourse.group/u/certik)\
**Post date:** [September 2, 2025, 1:44pm UTC](https://fortran-lang.discourse.group/t/its-2025-why-does-fortran-continue-to-dominate-weather-and-climate-research/10378/2 "2025-09-02T13:44:12Z")

</div>

This is great that this Discourse has such a good visibility. I now regularly find it in search results when I search about something Fortran related.

---

<div class="post-metadata">

**Author:** ![nbehrnd](https://avatars.discourse-cdn.com/v4/letter/n/e0b2c6/32.png) [@nbehrnd](https://fortran-lang.discourse.group/u/nbehrnd)\
**Post date:** [September 9, 2025, 6:45am UTC](https://fortran-lang.discourse.group/t/its-2025-why-does-fortran-continue-to-dominate-weather-and-climate-research/10378/3 "2025-09-09T06:45:35Z")

</div>

The comment by Katherine Zacapa below the publication on LinkedIn reads (emphasis added by me):

> When 80% of climate models run on Fortran and a full migration would cost $15M plus slow things down, _maybe Fortran isn’t legacy tech… it’s just the tech that quietly wins._

---

<div class="post-metadata">

**Author:** ![fxm](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/fxm/32/5726_2.png) [@fxm](https://fortran-lang.discourse.group/u/fxm)\
**Post date:** [September 9, 2025, 7:59am UTC](https://fortran-lang.discourse.group/t/its-2025-why-does-fortran-continue-to-dominate-weather-and-climate-research/10378/4 "2025-09-09T07:59:13Z")

</div>

It makes some good points, and I can confirm that some of these are raised when decisions are made to stay with Fortran in atmospheric research (even when we’re looking at building a model ~from scratch).

What bothers me a little about a lot of calls for migration (aside from Fortran-specific myths) is that they seem to operate on the assumption that moving from having a diversity of languages to a simply having C++/Python is somehow desirable.

---

<div class="post-metadata">

**Author:** ![certik](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/certik/32/4_2.png) [@certik](https://fortran-lang.discourse.group/u/certik)\
**Post date:** [September 9, 2025, 3:52pm UTC](https://fortran-lang.discourse.group/t/its-2025-why-does-fortran-continue-to-dominate-weather-and-climate-research/10378/5 "2025-09-09T15:52:18Z")

</div>

> [@fxm](#):
>
> they seem to operate on the assumption that moving from having a diversity of languages to a simply having C++/Python is somehow desirable.

I think it’s good to have less languages in the project. I would also remove Python and just use C++, then you only need people with C++ expertise, not C++ _and_ Python _and_ Fortran.

Our goal here is to ensure that the single language to use in a large project can be Fortran. So we need to have interactivity like Python (one of LFortran’s goals) and we need to have good modern hardware support (GPUs) and some language extensions like the traits proposal will also help.

---

<div class="post-metadata">

**Author:** ![fxm](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/fxm/32/5726_2.png) [@fxm](https://fortran-lang.discourse.group/u/fxm)\
**Post date:** [September 9, 2025, 4:21pm UTC](https://fortran-lang.discourse.group/t/its-2025-why-does-fortran-continue-to-dominate-weather-and-climate-research/10378/6 "2025-09-09T16:21:01Z")

</div>

Within a project, it makes absolute sense, but the sentiment I’m encountering more and more in conversations like these is that of “let’s migrate everything (not just this one project) to the same 1-2 languages“.

---

<div class="post-metadata">

**Author:** ![Carltoffel](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/carltoffel/32/1680_2.png) [@Carltoffel](https://fortran-lang.discourse.group/u/Carltoffel)\
**Post date:** [September 10, 2025, 8:54am UTC](https://fortran-lang.discourse.group/t/its-2025-why-does-fortran-continue-to-dominate-weather-and-climate-research/10378/7 "2025-09-10T08:54:26Z")

</div>

> [@fxm](#):
>
> “let’s migrate everything (not just this one project) to the same 1-2 languages“

This is especially true for Rust. Everything is “better” in Rust. Even fpm was almost implemented in Rust. 😂

 ![image](https://global.discourse-cdn.com/free1/uploads/fortran_lang/original/2X/9/9126e88731b8e6549f30e0542342ffc351221f68.jpeg)
