> They are still discussing whether to change something in a backwards-incompatible way in Go 2.

FTFY

Fortran from the 1980s is still supported...

Fortran from the 1960s is still supported. Almost all modern Fortran compilers support syntax that was deprecated decades ago.

You misspelled the 1960s.

Hell, I fixed something in Turing last week. My eyes are still bleeding.

And yet almost no one chooses to write new Fortran code for applications. We rely on a few ancient critical widely used libraries like BLAS, accessed from non-Fortran programs.

This is not true, there are niches where Fortran is still dominant for new code.

Also for BLAS, the underlying code is usually no longer Fortran.

I came to say this. I learned Go in the early years and have come back after not touching it in years and it all still sounds eerily familiar and a lot of the basics I learned are still relevant to what I do.

Go is good at being Pythonic in some senses too. Some would say to a fault.

They probably do not want to end up with a Perl 6 situation. I meant Raku, the language formally known as Perl 6.