#fortran

@loke @cobolworx

So now one of the reasons for GNU #FORTRAN is gone:

Keep hearing whispering voices "GNU COBOL, GNU COBOL"

@mattgemmell Surely you mean 64x16.

Yes, that is Fortran. On the Radio Shack TRS-80. My first programming job.

#trs80 #fortran

New blog post: #Conda + #Fortran

https://degenerateconic.com/conda-plus-fortran.html

#Elvis's first appearance on Sullivan, 1956-09-09

For a bit of perspective, this was 1 year before #FORTRAN came out.

https://youtu.be/u90bPXAdt1o?si=XXnY78ozO22zG1oU&t=206

#Jupyter notebooks support #Coarray #parallel #Fortran kernel.

https://github.com/sourceryinstitute/jupyter-CAF-kernel

I'm an HPC user of CPU Fortran compilers, and my primary/preferred compiler is__________"

#HPC #fortran

Porting COBOL Code and the Trouble With Ditching Domain Specific Languages - Whenever the topic is raised in popular media about porting a codebase written in ... - https://hackaday.com/2025/04/16/porting-cobol-code-and-the-trouble-with-ditching-domain-specific-languages/ #softwaredevelopment #featured #interest #gnucobol #fortran #cobol

Was für eine Freude. Mal wieder alten #fortran Code debuggen.

Does anyone know a specific version of fortran or algol that does not have "for" as a reserved word, so it can be used as a variable or something, I need it for an exam. #programming #fortran #algol

I would be a greybeard #UNIX guy if I could grow a non-scraggley beard, and it's unfair to the #DOGE teens to claim that the IRS and Social Security rely on ancient #COBOL code that only a few people alive actually understand. They also rely on ancient #FORTRAN code and even I never studied that at Computer Camp.

Pondering if I dare to put #Fortran into my CV.

I can do some Fortran, partly because it keeps coming up in all sorts of #retrocomputing contexts, but, even with Ratfor enhancements, I don't consider it a well-designed or pleasant language, and I'm not sure I can see myself working at a place that deals in new Fortran code now that nice, human-friendly languages such as NumPy and APL have been invented. Besides, 21st century Fortran is a really weird language that doesn't even know what it wants to be when it grows up.

@bbatsov Exotic languages like #Fortran and #Cobol.

Every language can be exotic if you wait long enough! :)

The original #LISP had 7 primitives: \(\texttt{cons}\), \(\texttt{car,}\) \(\texttt{cdr}\), \(\texttt{atom}\), \(\texttt{quote}\), \(\texttt{eq}\), and \(\texttt{cond}\). And the original #Smalltalk syntax could fit on a 5×7 card. That meant a novice could learn the syntax in a matter of minutes, and direct all his efforts to learning how properly to wield the power of that Turing-complete language. This was why, in the 1970s and the 1980s, many college freshmen were taught FP in Scheme (a more modern LISP) and many middle school children were taught OO in Smalltalk. These were surely the best "first" #programming languages.

#FORTRAN and #BASIC were simple, too. FORTRAN, the first high-level language, has been in continuous use since the late 1950s by engineers, who are not keyboard warriors. BASIC was invented in the early 1960s for teaching programming to non-STEM students at Dartmouth. It sired a whole generation of self-taught children in the 1980s.

Compare those to C++, Erlang, Python, Haskell, Java, JavaScript, Scala, Rust, Kotlin, and pretty much every language in popular use today. Most consider Python and JavaScript to be the simplest of modern languages. Yet, they are massive, complex languages. No 10-year-old could teach himself those, nor should he.

The original versions of those classic languages cannot be used to solve modern problems. But they should still be taught to youngsters as their first language. Throwing in the kids' faces a modern enterprise language confuses them and discourages them. Consequently, many novices never attain that state of flow, when the joy of programming gushes forth.

#Simplicity is a virtue. Self-motivated learning is virtuous.

@michalfita @b4ux1t3

#Fortran? I haven't used punch cards in many years. ;-)

Fortran IV WATFIV

@b4ux1t3 #Crystal is not very popular, but worth a shot. Some people could point at #Nim as well. There was a time #Kotlin could be natively statically compiled, but I don't think JetBrains maintains this.

From the museum you could try #Ada or #Fortran - modern one is supposedly very nice language (I haven't tried).

I predicted¹ in 2014 that #julialang might replace #Fortran for #science and #engineering calculations. I think this process has begun and will continue.

Get a solid foundation in Julia (or any) language by starting with a good book:

https://lee-phillips.org/amazonJuliaBookRanks/

[1] https://rb.gy/y7yr2j

@peron #fortran en #Debian lo usé con gfortran, no encontré el compilador f95 que decía la página y funciona igual.

Haciendo los palitos con Cobol y Fortran, gracias a @peron #fortran #cobol

Writing a commandline tool in #Fortran:
https://www.draketo.de/english/free-software/fortran

In case you want to broaden your #programming skills. Fortran seems to be making a comeback (currently 11 in the Tiobe index: https://www.tiobe.com/tiobe-index/fortran/ ).

This is from 2017, written at the end of my Physics PostDoc where I used quite a bit of Fortran and learned to appreciate it much more than I expected.

FORTRAN package manager in Guix?

https://github.com/fortran-lang/fpm

https://stackoverflow.com/questions/79357849/how-to-package-the-fortran-package-manager-for-gnu-guix

It's backed by https://www.sovereign.tech/tech/fortran

@abcdw

#Guix #fortran