Live data from Hacker News

Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran

github.com

1–10 of 91 posts

Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran

#3

out of curiosity, why fortran? no disrespect. I wrote a lot of scientific software in the earlier days of my career and I learned fortran to update ocean modeling software.

maybe they weren't really concerned about portability or a decent standard?

Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran

#4

out of curiosity, why fortran? no disrespect. I wrote a lot of scientific software in the earlier days of my career and I learned fortran to update ocean modeling software.

> 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 client written in Fortran

#6

out of curiosity, why fortran? no disrespect. I wrote a lot of scientific software in the earlier days of my career and I learned fortran to update ocean modeling software.

You are not the first one to ask :)

We built Cobolsky. Will go public soon. Parallelly too curious on Fortran. The world is better with a Fortran-based social network client in it :)

When we are building the feed composer, in next version, Fortran will be great for the algorithm etc.

Keeping the ancient languages alive. I built some Cobol stuff many years ago. Back at it again. Rusty.

Both Cobolsky and Fortransky looks great on Swordfish90’s cool-retro-term, but we are building our own terminal for Fortransky too. There is a blog post with screenshots over at Patreon/formerlab

Can’t get enough Fortran

Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran

#7
post #4

out of curiosity, why fortran? no disrespect. I wrote a lot of scientific software in the earlier days of my career and I learned fortran to update ocean modeling software.

> 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.

Fortran will survive the cockroaches even, when the world 404s

Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran

#8

out of curiosity, why fortran? no disrespect. I wrote a lot of scientific software in the earlier days of my career and I learned fortran to update ocean modeling software.

You are not the first one to ask :) We built Cobolsky. Will go public soon. Parallelly too curious on Fortran. The world is better with a Fortran-based social network client in it :) When we are building the feed composer, in next version, Fortran will be great for the algorithm etc. Keeping the ancient languages alive. I built some Cobol stuff many years ago. Back at it again. Rusty. Both Cobolsky and Fortransky loo…

> The world is better with a Fortran-based social network client in it

If you don't mind me asking, why is the world better with more Fortran-based software?

Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran

#9

out of curiosity, why fortran? no disrespect. I wrote a lot of scientific software in the earlier days of my career and I learned fortran to update ocean modeling software.

maybe they weren't really concerned about portability or a decent standard?

It’s keyboard navigation only, and we got the Bluesky firehose raw straight into the Rust decoder. Or we switch mode to Jetstream with m+EnTER :)

You hit l+ENTER to like a post. If anyone replies from Bluesky, we hit n+ENTER and see the notifs. And so on

Fortransky is 70% Fortran, rest is Rust, C and a tiny Python helper

Post reply on HN