Ok, you caught us. It certainly isn’t going to be the year of Algol. When you think of “old” programming languages, you usually think of FORTRAN and COBOL. You should also think of LISP. But only a few people will come up with Algol.

While not a household name, Algol was highly influential, and now, GCC is on the verge of supporting it just like it supports other languages besides C and C++ these days. Why bring an old language up to the forefront? We don’t know, but we still find it interesting. We doubt there’s a bunch of Algol code waiting to be ported, but you never know.

Algol first appeared in 1958 and was the lingua franca of academic computer discussions for decades. It was made to “fix” the problems with Fortran, and its influence is still felt today. For example, Algol was the origin of “blocks of code,” which it set between begin/end pairs.

The second version of Algol was where Backus-Naur form, or BNF, originated—something still of interest to language designers today. Interestingly, the new compiler will support Algol 68, which was the final and not terribly popular version. It was sort of the “New Coke” of early computer languages, with many people asserting that Algol 60 was the last “real Algol.”

Algol was known for sometimes using funny characters like ≡ and ⊂, but like APL, it had to adapt to more conventional character sets. Most of the Algol specifications didn’t define I/O, either, so it wasn’t enough to just know Algol—you had to know which Algol to understand how the I/O worked.
https://hackaday.com/2025/10/15/could-this-be-the-year-of-algol/