Live data from Hacker News

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

github.com

31–40 of 91 posts

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

#32

Earlier quoted context omitted.

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

Our modern languages are built on it, and it’s incredibly fast, so it deserves to be kept alive. We owe a great deal to the people who wrote it in the 1950s I guess

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

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

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

Great, can we see some benchmarks?

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

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

Post reply on HN