News for hackers. Stuff that matters.
Re:Show HN: We built a terminal-only Bluesky / AT Proto clie... by enriquto on Friday March 20, 2026 @06:21PM (#47461485)
> why fortran?

why not? the language is straightforward and loops are fast. It is portable and your code will work unchanged for the next 50 years. It may be a bit verbose, but that's not a big deal with today's tooling.

Re:Show HN: We built a terminal-only Bluesky / AT Proto clie... by FormerLabFred on Friday March 20, 2026 @06:27PM (#47461548)
Fortran will survive the cockroaches even, when the world 404s
Re:Show HN: We built a terminal-only Bluesky / AT Proto clie... by pklausler on Friday March 20, 2026 @06:35PM (#47461663)
Your code will work unchanged until you try to change compilers or your compiler adopts a J3 breaking change to the language.
Re:Show HN: We built a terminal-only Bluesky / AT Proto clie... by kergonath on Friday March 20, 2026 @08:02PM (#47462524)
> your compiler adopts a J3 breaking change to the language

Like all the 3 of them they added in the last 30 years, and that compiler vendors are not enforcing anyway because they don’t want to annoy their users?

Windows’ backward compatibility is a joke compared to Fortran.

Re:Show HN: We built a terminal-only Bluesky / AT Proto clie... by pklausler on Tuesday March 24, 2026 @02:35PM (#47507156)
We're definitely enforcing some of them. But the latest one from F'2023 isn't going to be.
Re:Show HN: We built a terminal-only Bluesky / AT Proto clie... by deadbabe on Saturday March 21, 2026 @12:23AM (#47463967)
Great, can we see some benchmarks?
Re:Show HN: We built a terminal-only Bluesky / AT Proto clie... by FormerLabFred on Saturday March 21, 2026 @05:04AM (#47465355)
Cobolsky holds the record for most surprised looks per line of code :)

Fortransky benchmarks pending

the feed scorer will have real numbers worth reporting

Whenever time allows in future: Fortran vs Go vs Python

Re:Show HN: We built a terminal-only Bluesky / AT Proto clie... by foxglacier on Saturday March 21, 2026 @02:09PM (#47469599)
Yea na, Fortran is pretty compiler dependent and there are a lot of compilers. Already old Fortran code used all sorts of now-dead proprietary compilers and can take a huge effort to get it to compile on modern compilers or even modern computers. Modern code might use Gfortran which sometimes makes breaking changes so that's not an option. Perhaps if everyone uses the latest shiny new Flang or whatever, then it'll finally last 50 years? Not likely, given the history.
Re:Show HN: We built a terminal-only Bluesky / AT Proto clie... by pklausler on Sunday March 22, 2026 @10:04AM (#47477673)
For a standardized language, Fortran isn’t very portable across compilers. GNU Fortran has done a great job supporting legacy features, and I hope that our work in flang-new has made it easy to port to, as well. I basically ignored the zealots who wanted flang-new to be a strict compiler by default. The hobbyist project LFortran is quite the opposite, and will yell at you by default for perfectly conforming variations in keyword spelling. For those who like that sort of thing, that’s exactly the sort of thing that they like.