- I find it useful to discount heavily for hyperbole when reading stuff written by Amiga people, including the otherwise essential Bagnall books. I think the shock of being able to do multimedia-ish stuff in the mid 1980’s somehow causes reality to distort when considering the stunning mediocrity (or worse) of much of the AmigaOS software stack.
(I can write some choice words on the Mac’s software stack too. None of the 80’s 32-bit platforms were without significant and avoidable problems.)
edit: misplaced punctuation
- I dunno, I thought the PSP was just ill-conceived and pointless at the time. Sony was at the peak of their NIH syndrome, and just not caring what the market actually might want.
- I object to the premise.
> Configuration options and user empowerment was increasingly considered confusing or dangerous
This, in particular, is nonsense, but it’s a long-festering strain of nonsense. A particular subset of PC users truly believe that Apple decided, with the original Mac, to take away “user empowerment” and “dumb things down” because users might hurt themselves. That was never the motivation.
No, the point was to empower users in ways that actually mattered. Steve Jobs’ “bicycle for the mind” rhetoric was trying to communicate this. You can disagree with the selection of what, exactly, matters, but the underlying motivation was _never_ to “protect users from themselves.” That’s a canard.
- Well, look at the critique when Gnome3 came out to replace Gnome2. What pissed people off was exactly that it: 1. Set a certain amount of choices on how the gui should work and 2. Removed a lot of settings, especially those that would have allowed people to reset the things in point 1 to what they liked from Gnome 1&2.
It's one thing for a GUI maker to move the task bar from side to top/bottom for instance, but another to also not allow you to have it back where you "need" it to be. Even when you do want to move defaults (like tmux changing hotkey from screens ctrl-a to ctrl-b) it still is a good idea to allow people to set it back, even if only for a transitional period. Muscle memory takes a while to change for some, and GUIs are not except from that, so if you always had the trashcan to the right, moving it to the left will piss someone off, but not as much as preventing that someone from moving it back again, if that is their preference, perhaps even a preference that your previous versions of the GUIs made for them.
- But that passage doesn't refer to the original Mac. It describes notions that started becoming commonplace around 2000, and the end of that paragraph specifically differentiates them from the Mac Classic era.
About the argument in general, the false premise would be that the set of things which "actually matter" applies universally. It's not a question of what exactly matters, but _to whom_. There are different types of users, and the pretense of always knowing what's good for all of them better than those users themselves is certainly not unique to one person's approach... even if Jobs' personality could make it appear as if he had it worse than most others in the industry.
- I’ve lived the dongle life for 40 years because Steve jobs didn’t want people tinkering with the insides of the Mac. My ProFile and HD20 is testament to that.
- The BeFS book mentioned referenced in the article is still a terrific read.
- I think it would be swell if we could avoid fascist-adjacent slogans for retrocomputing projects.
- Apple Pascal supported > 64k of RAM on suitable machines, so it probably already did?
- Apple Pascal on the Apple II was restricted to 64 K memory; this limitation was due to the 6502's 16-bit address bus. The Apple III with it's 6502A could address 256 K, but only by bank switching; pointers remained 16-bit. The later Pascal versions (after Apple III) did no longer use P-code, but compiled to native code.
- There was a 128k version of Apple Pascal available on the Apple II. My question, applicable to both this and the Apple III version, is: Was the bank switching managed by the developer or by the Pascal runtime? If it's managed by the runtime, the addresses must have been encodable with >16 bits.
- All versions of Apple Pascal use 16-bit pointers, so data was always limited to a 64 KB address space. On the 128K Apple II, p-code was located in aux memory, and data was located in main memory.
Apple III Pascal had similar limitations, with separate 64K address spaces for p-code and data. On machines with more than 128 KB of RAM, there were assembly routines available for allocating additional memory and swapping data memory.
- I would only add that the iPod is what saved Apple, not the Mac. NeXT’s software didn’t really have anything to do with it. Most Mac users stayed with Mac OS 9 until 2003-2004, because OS X wasn’t ready for prime time until then.
In terms of Apple’s long term survival, everything Apple did between 1997 and the iPod introduction was just treading water. Steve had stopped the bleeding, but the Mac was still not setting the world on fire in terms of market share or profitability. It was on shaky ground until the Intel transition, coupled with the iPod halo effect, allowed people to feel safe buying Macs again.
- > I would only add that the iPod is what saved Apple
Yes, I agree. I just didn't want to get into a lot of detail in what was basically an aside to address that Apple's Mac platform did (sort of) survive. But as you observed, it was on very shaky ground and hardly a resounding success. Even today, the Mac business isn't as significant to Apple as iOS or services.
- iPod was a halo effect. it gave people a reason to buy a mac. Just like Microsoft sold things to bundle together. Outlook is best when you buy it and use it with Exchange.
- > That’s because in some ways, the ST and Amiga were better than a PC running Windows 3.x. If you didn’t experience it, that statement sounds absurd. But if you experienced it, you totally know what I mean
Do people really find that absurd? I was a Mac user, but I've never seen anyone seriously argue a PC with Win 3.x was better than Amiga or the ST. It was ubiquitous, but it was both less pleasant to use and uglier than practically any contemporary non-x86 option. It's not like Microsoft wasn't trying, of course; Windows had to run on commodity PC hardware designed to run DOS, which meant a wide variety of potential hardware had to be supported or supportable; the Mac, the ST and the Amiga each had a single hardware vendor.
- In 1985 Windows 3.x was still far in the future. The closest thing to ST/Amiga in the PC world was GEM - until Apple sued DRI and made them cripple it.
- my psion 3a was better than win3.x :-)
i could have spreadsheet, database, agenda and word processor open and swapping between docs instantly while my win3.x desktop lurched and trashed disk with just 1-2 windows open. also win3.x at the best of times was pretty crashy. a few reboots a day was quite common.
plus memory. some programs wanted expanded, some wanted extended so you ended up with multiple boot configurations, some for games, some for windows, some for dos apps.
- The Psion 3 series used 8086 processors, so they could have released a standalone version of SIBO for IBM-PCs with relative ease.
In fact, Psion did release a SIBO "emulator"* for DOS which seems to be basically a PC port. It's intended for developers, and hews to replicating the mobile devices rather than taking advantage of the PC hardware, but you can imagine polishing it a step further.
- Yeah, I tried to use Windows prior to 3.1 a few different times and never made it past the first five minutes. While Windows 3.1 was significantly better, I still bailed out after an hour. By the early 90s I just wasn't willing to slip that far backward compared to the more mature, complete and useful options I was familiar with. It wasn't until Windows 95 and the Pentium that I could adopt the PC as one of my main daily drivers.
- This is great; it's really well sourced. Check out the footnotes for additional reading material.
- Does anyone know what games the Unix Z-Machine originally shipped for, if any, and for which machines? There wouldn't have been high demand in 1985 for a Unix version of Infocom games (understatement). There are mentions of the "AT&T PC" in the source, and a snippet of 68000 assembly language.
There's a Fooblitzky interpreter too, but that didn't ship for anything Unixlike.
- When the game Beyond Zork starts up, it asks the Z-Machine interpreter what platform the interpreter is running on. If it's a platform that supports graphics, the game uses a custom font to draw an on-screen map; if it's a platform that only supports text, it does not try to draw the on-screen map. If it's a VT220, it uses the VT220's built-in special characters to draw the map.
Probably nobody was buying a special VT220 edition of Beyond Zork, I think that version was used by the developers working at Infocom, who did their work on a minicomputer and terminals. I believe it was a VAX, rather than a Unix minicomputer, but it wouldn't surprise me if the Unix Z-Machine interpreter had a similar story behind it.
- Beyond Zork’s map drawing code will also produce an ASCII art variant of the map for systems that can’t easily handle the custom font, like, IIRC, the Apple II.
The Infocom dev machine was a DECSystem 20 (PDP-10 architecture) until circa 1988, when they ported tools to the 68020-based Mac II.
I expect they thought the Unix source would be a good basis for future non-Unix development; comments in the source itself allude to this possibility; I’m just wondering if it was used in any shipping product. I suspect it wasn’t.
- I actually don't think any UNIX variant ever shipped as a commerical product. My gut feeling while working on the project was that it was perhaps a reference implementation, documenting proper z-machine behavior the various assembly versions needed to match. But that's a literal guess, TBH.
The list of known system codes (used as identification for packaging and so forth) can be seen here: http://pdd.if-legends.org/infocom/fact-sheet.txt
- More
sony makes beautiful hardware, some of the best. but they destroy it with bad practices like cd players that can't read cd-rs. digital music players that weren't mp3. they became about protecting their copyright and not doing what their customers wanted.
For a while, I had a SONY CD Changer in my car. You ever see the scratched up CDs often sold at flea markets for a buck each or less?
Many computers and players won't read them.
But that SONY does. And not only does it read them, the thing takes a bit longer to buffer due to all the scratches and massive error correction it has to do while buffering...
But once it does all that, it will play the disc flawlessly! Bumpy roads, too cold, too hot, disc too scratched?
All pretty much no problem.
I would gladly buy another. Was that good, but it won't read ANY recordable format.
Bummer.
It went with the car when I sold it. I put some of the very worst discs I had ever seen in it for demo purposes too.
Dude that bought the car loved it like I did. I did not mention CD-R largely because the player was going with the car no matter what.