Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran
31–40 of 91 posts
Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran
#32Earlier 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
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
#33Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran
#34Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran
#35Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran
#36out 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
#37Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran
#38- VCs band together to fund something shiny.
- Devs love shiny, helping spread the something.
- VCs enschitify it to get their coins back.
Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran
#39Re: Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran
#40The 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.