@mattgemmell Surely you mean 64x16.
Yes, that is Fortran. On the Radio Shack TRS-80. My first programming job.
@mattgemmell Surely you mean 64x16.
Yes, that is Fortran. On the Radio Shack TRS-80. My first programming job.
Wow, #fortran has moved a long way since I last used it! That it now has a package manager is brilliant!
Now to find a project using Fortran, so I get to play with it again
Oh joy, let's redefine "recursion" by talking to a robot in English while pretending it's 1965 and #FORTRAN is cutting-edge! Because if there's one thing developers need, it's AI-powered verbosity!
https://github.com/andyk/recursive_llm #recursion #AI #verbosity #techhumor #HackerNews #ngated
I'm an HPC user of CPU Fortran compilers, and my primary/preferred compiler is__________"
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
Ah yes, because nothing screams "wild adventure" like trudging through the annals of punch card history and FORTRAN's glorious miseries.
Apparently, teaching #programming in the '60s involved more paper jams than Indiana Jones had snakes.
https://bluerenga.blog/2025/04/03/the-troll-hole-adventure-1980/ #punchcardhistory #FORTRAN #education #techhumor #codingadventures #nostalgictech #HackerNews #ngated
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.
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.
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
I don't remember much about #Markov Chains, #Random-Walk. Fokker-Planck. Jeez Louise. Scratched around trying to read and understand stuff. Fortunately at the time, my advisor cleared the decks, said don't bother, here is a 2-D #Gaussian dispersion model I wrote in BASIC. Re-write it in #FORTRAN and add two flavors: a #Lagrangian and a K-theory particle dispersion model, for a convective boundary layer. Use those formulations for a connective boundary layer you learned in Turbulence.
Will #Fortran back?
All languages have life cycles. Hell, some even go dormant and become popular — or unexpectedly critical – again.
What would qualities would a language need to have to eventually threaten Python's dominance? My fear is any innovative ideas will just get absorbed. Yes, I realize much of #Python's muscle is marketing by big industry players.
Any #OpenMP lawyers?
Is this not legal?
nvfortran complains that nloop is not shared or private. Do loop trip-counts really need to be?
And for reduction variables (loopsum) too?
program test_omp_private
implicit none
integer :: iloop, nloop
integer :: loopsum
nloop = 10000
loopsum = 0
!$omp parallel do default(none) firstprivate(loopsum) reduction(+:loopsum)
do iloop = 1,nloop
loopsum = loopsum + iloop
end do
!$omp end parallel do
end program
For a periods in the late 80s, early 90s, late 90s, and early 2000s, I was a professional #Astronomer (yet another workstation jockey) with a particular interest in #BioAstronomy -- planets, star forming, potential habitats -- that sort of thing.
Used data-reduction software. And I wrote some in #FORTRAN
Along the way, also learned BASIC, C, C++, Pascal, and then #Python
Helped develop the #NICMOS camera for Hubble. Then got to reduce some data from it to study protostars.
[2/3]
#lispyGopherClimate #podcast #archive https://archives.anonradio.net/202501150000_screwtape.mp3 0UTC Wed
#interview ing @shizamura author of the popular #scifi https://sarilho.net/en/ #comic
#climateCrisis #haiku by @kentpitman
#liveChat in #lambdaMOO as always
telnet lambda.moo.mud.org 8888
co guest
@join screwtape
#Questions for @shizamura please!
#lisp, #fortran, #grammars, oh my.
#Murderbots #bookstodon @nosrednayduj @dougmerritt @ratxue @mdhughes I finally read 90% of it (no spoilers please)
Oh the shame, running on autopilot I just started writing a #Fortran subroutine with def.
Maybe time to go back to bed, or just not write any python for a while.
More seriously, there is perhaps something to be learnt from this about #ContextSwitching, and a sweet spot of not too short so as to build focus, not too long to forget details, but finding a Goldilocks zone for me as an individual.