Project Aon is an effort to post the old Lone Wolf game books to the webpage medium...
I'm also seeing similar book apps in the App Store which give the player a chance to pick starting stats to influence gameplay progression. (One I found involved the player RPing as a dragon, hoarding treasure and defending territory from other dragons and human kings and wizards. I forgot the name, though.)
The amount of work involved in upgrading a Mac has, usually, been excessive.
This has only been true historically with the consumer models. The models that Apple designates for "professional" usually upgrade much easier. My current G5 has full access from a side door (as well as the current Mac Pro line) and even my old LC and 4400 had easily accessible PDS and PCI slots when the case is slid off. (My iMac G4 was the only machine I had I couldn't upgrade myself.) It's just that, as the "ease of use" brand in the industry, Apple's more famous machines are the all-in-one and laptop units that have the more cramped assembly and design.
It really is frustrating how intensely climate science is doubted and denied. Economics - a far softer science with a (so far) vastly greater impact on human society - gets a staggering amount of leeway by comparison.
Because of its scope and visibility, disciplines like Economics can get away with the Big Lie effect. Climatology, which is more subtle and relatively young, suffers from the Cassandra problem instead. Sad, but true...
Oh my goodness, did they really write it in assembler? I always imagined they already used high-level languages at that time.
I don't remember high level languages being considered "proper" for commercial development until the late 80's at the earliest. When the Mac was first introduced in the mid-80's, it was still considered important to write all the system and OS code in 68k assembler, with apps only begrudgingly being written in Pascal. And on the PC side, games and certain networking heavy apps were still written in x86 at late as the mid-90's. It was only with C, which was originally considered a "high level assembler" did many development houses consider such programming "real" development. (And even into the late 90's, I still saw inline assembler used in places for "performance reasons," an idea not taken seriously anymore by most due to how compilers have advanced in recent years.)
We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise. -- Larry Wall