Love seeing niche Show HN projects like this. The choice of Fortran is wild but that's what makes it fun. As someone building small Mac utilities, I appreciate any project that proves you don't need a massive stack to ship something useful.
AT Protocol is a joy to build on — open public data, structured JSON, zero auth friction. I built a Bluesky scraper using the same endpoints and it's one of the most stable scrapers I have. Great to see more tools for this ecosystem.
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.
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
It's part of the lineage, yeah, probably started with Algol though? Fast I guess is always nice, but I'm not sure that's enough to keep it alive solely for that, at least to me.
I came here to suggest COBOL as a better fit, then saw your comment a few levels up in this thread.
Out of curiosity, does your implementation use CODASYL?
(For people that don't pay much attention to historical software systems, most CODASYL implementations were similar to JSON document databases, so going that way isn't as crazy as it sounds.)
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.
> 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.
From my experience building browser automation tools, the biggest challenge with most Chromium-based solutions is that their TLS fingerprint is a dead giveaway. Firefox-based approaches tend to fare much better against JA3/JA4 fingerprinting.
The key insight is moving fingerprint spoofing from the JS level (which is itself detectable) down to the native C++ level. It's a fundamentally different approach.
