Sweet! Yeah, I think you've answered most of my questions -- enough to have a very basic understanding of it, anyway. It's always better to know than not to know, that way you can appreciate both the similarities and differences, and appreciate the approaches where they differ.
...
...
I'm not super well-informed, but the basic idea behind #PermaComputing is to be the very opposite of the upgrade treadmill -- to have a system of computing that does not have to be upgraded every year, or even every decade. To have software tools that can run on any kind of hardware you throw at it, from 16-bit microcomputers to handheld game machines of today and yesteryear, to raspberry Pis and even modern machines.
...
...
The goal is to reduce/eliminate e-waste, and to have a software ecosystem that is resistant to supply chain constraints or even collapse. I think a subculture of #PermaComputing is what you might call #CollapseComputing (not certain about the terminology there) -- creating software tools and hardware flexibility that can survive even the total collapse of the modern economy and supply chain -- think Mad Max with computers, haha.
...
...
You get a 16-bit virtual CPU with (I think) wavetable sound, 4-color (4096-color palette) graphics with very flexible resolution, 64KB RAM with no storage constraints, and a stack-based reverse polish Forth-style assembler with 32 opcodes * 4 total modes (IIRC). There are of course C compilers for it, and probably some higher-level languages as well.
...
...
So, you write one piece of code, compile it to a single binary, and it can run on a modern laptop, and Amiga computer from the 80s, a Gameboy Advance, a Rasberry Pi, you name it. With the same computational, graphics, and sound capabilities (with obvious caveats on more limited hardware).
There's even a classic macintosh-inspired GUI OS / file browser for it.
...
...
It's cool stuff. It scratches a lot of itches -- a kind of alternate-history retrocomputing, learning assembly language, enjoying a programming challenge, writing freaking EFFICIENT code, you name it. :D
R. L. Dane 
Crunchysteve