I was hoping for a secret society of volcano watchers, handing down carefully guarded records from generation to generation . . .

("There's nothing written in here, Dad")

Old enough here to remember Intel entering the DRAM business :-)

I use an HP-16 (the SwissMicros version, my originals are in boxes) and a 35s pretty much every day (these days, I'm writing firmware).

Henry S F Cooper wrote a wonderful account of debugging OS race condition on the Magellan (Venus) orbiter in The Evening Star

I've built and maintained similar setups (10PB range). Honestly, you just shove disks into it, and when they fail you replace them. You need folks around to handle things like controller / infrastructure failure, but hopefully you're paying them to do other stuff, too.

my dad was an ecologist in the 70s, and did a lot of early climate change stuff (getting ground truth for LandSat, etc.)

that's always been a fun conversation

That does sound super interesting.He probably had a real fun time doing science in the 70s.

> My problem is that I cannot see how control flow works in Forth, e.g. a simple if-then-else.

figuring this out for my own FORTH interpreter was a moment i still remember, nearly 50 years later. quite a revelation

In my opinion, a language that requires a programmer to have a "revelation" to understand basic control flow is not a language that is useful or practical for solving real world problems.

I would prefer to write in assembly language than write in Forth. Which is what I have done with one of my current projects.

With assembly language, there is a good chance that a random person with some minimal programming skills would understand my program if I were hit by a bus. With Forth, I think the chances of that are close to zero.

If you're coding, you don't have to understand how to implement control flow. The average C programmer hasn't a clue how the underlying control flow is implemented. It's an _implementor_ of an interpreter or compiler who needs to understand this. Forth is no different from C or any other language in this regard, except that, in Forth, control flow can be implemented directly rather than relying on the compiler or interpreter to understand them.

Immediate words are essentially a kind of macro, if it makes things easier for you.

I remember, many years ago, when I was learning programming. When I grokked recursion, it was a revelation to me. Could I be a programmer without that revelation? Yeah, kind of, but I'd be a lesser one.

i understood how to use IF/ELSE/THEN in FORTH. my "revelation" was figuring out how to do the code generation for it. i was in high school :-)

i definitely prefer assembly to FORTH. i have direct and rather terrible experience with this after watching a few people try to ship a cartridge video game in FORTH

It's a revelation to understand how basic control flow is implemented in any compiler. From your described preference to not learn things that aren't generally known, it's a safe bet that you don't understand CPS or SSA either, or know what a basic block is.

in 1978, emacs was a possibility

but i'm gonna guess SOS or TECO, if they were running a bog standard PDP-10 OS from DEC

i have maybe $15K in Synology gear. it's getting old and should be replaced with something with better efficiency

the replacement will NOT be from Synology