> What is this obsession with the past and the early days of computing?
Sure, no need to study history. Just pull to refresh every second and don't remember anything. And also, defund the national archives too, they are apparently useless.
/s
Sure, no need to study history. Just pull to refresh every second and don't remember anything. And also, defund the national archives too, they are apparently useless.
/s
We are now operating in an environment where the average programmer is writing using frameworks on top of frameworks, on top of libraries, on top of SDKs, on top of containers, on top of VMs, on top of OSs, on top of hypervisors, on top of kernels, on top of microcode, and that's collapsing a bunch of the layers.
To have any hope of explaining to the next generation how many of the truly beautiful and fun aspects of computing systems operate, you need to strip away many of these layers.
A great way to do that is with old systems where the layers didn't exist.
"<Sigh>if you only knew." - Guy who did his capstone project on neural networks and computer vision in the 80s.
If you use a CLI - you need to go back to at least teletypes.
Not everyone needs to be concerned with this, but the historical examples of cultures that have throw away their history don't look too encouraging.