Thee problem is the viewer, not the format.
We are talking about accessibility and scientific papers, where fancy animations and transitions are not core features.
LaTeX and TeX are the de facto standard for this context and converting all existing documents is a lot of work and energy to be spent for basically little gain, if any.
Unfortunately, I am working for an aerospace manufacturer that runs VAX VMS on emulators (which are quite expensive). We also run an even older operating system, OS2200.
The original VMS system manager who moved from 7000 series hardware to emulation was somewhat inquisitive, and we did install VMS 7 on simh. He retired and passed away some years ago, and none of his replacements have wanted to touch simh. I find that apathy appalling.
In 1990's, maybe. Today simh-classic it's serious stuff up to the point a fork was made because some nut tried to tamper 1:1 disk/tape images with custom headers.
That's why so many of these new age development tools, libraries and abstractions are such incredibly janky pieces of bloat that literally require what a few decades ago was supercomputers.
For me, it's a chance to experience what it was like to use and develop software on these systems back in the day. For example, lately I've been writing some small apps and adding new kernel features to a variant of V6 Unix running on my PDP-11/05. It's humbling to see what it really took to be productive on these systems.
Some people even did y2k patches to BSD 4.3. Also, tons of 'modern' software could run on it you can get GCC 2.95 and GCC 3.4. Lynx, for instance. Or gopher and IRC clients. And, maybe, with a bit of luck, Lua and JimTCL.
Understanding, and inspiration. They had to create under serious constraints in compute, memory, and storage, and understanding how and why they did can lead to ideas about how to optimize software on modern machines.
It's also critical for understanding how and why the engineering choices were made when documenting the evolution of processing. Instruction sets, processor design, programming languages, computer culture, corporate trends, all of those things have roots in design decisions, and the software preserved on tapes like this are a sort of DNA.
The effort needed to incorporate the information is dropping, with AI you can run analysis and grab important principles and so on, and whatever principles govern optimization and performance under constraints will be useful on a permanent basis.
You never know what will be important to people in the future.
I just listened to a great new episode (podcast) of The Truth (audio drama anthology series, they’re fantastic). It was called “The Joke.” Basically this archivist finds an old hard drive with a dumb pun joke - turns out she didn’t even understand it because jokes were no longer allowed in society. Kind of has an Equilibrium vibe but more bureaucratic and less “killing people for feeling.” Anyway the joke itself takes on great importance as a result. Bit of a dramatic comparison, but you see what I’m driving at.
We shouldn't rely on YouTube to write our history. It's just an American entertainment website that makes money of ads. It has no other obligations. It can do whatever it wants, or what the US government wants. This is not news.
I'm sure it's technically true, with absolutely no nuance. You can say "BBC pull documentary of life inside gaza" which is completely accurate. What is also true is that the boy who was the main focus of the documentary was the son of a Hamas official which throws the whole thing into question.
YT normally takes down any video depicting violence.
I too have spent hours of assembly code on PC hardware. My freshly downloaded copy of the interrupt list has always been at my (virtual) side when designing tests or libraries.
I think that has been one of the very first and largest information collection shared for free on the internet.
Kudos to Ralf Brown and whoever participated in keeping the list compete, accurate and timely.
It is not clear to which problem.
reply