Cosmic Conservative

Rational Conservatism from the heart of America

End of an era...

By CosmicConservative
Sigh, after trading my trusty four-year-old iBook for a Compaq laptop at lunch today I find myself not having an active Macintosh computer to use for the first time since August of 1984. That's 22 years follks. Wow. Steve Jobs should take notice. Here is my "short list" of Mac computers I have owned: Macintosh 128K original 1984 model (I do still have this, but it isn't really usable anymore. Over the time I owned it I upgraded it all the way to a Macintosh Plus.) Macintosh II, again the original version. I'll never forget when I ran a particularly complex spreadsheet on my new Mac II that took several minutes to run on my upgraded Plus and it recalculated so fast that I didn't see it at first and thought the computer was hung. I thought I had achieved nirvana when I realized it had actually calcuated the spreadsheet literally a thousand times faster than my "old" Mac. Macintosh PowerPC PC/Mac dual boot. I don't recall the model number now, but it was the first non Motorola 68000 based Mac. It also had an Intel 80386 chip in it and you could actually run PC and Mac programs simultaneously. Macintosh iMac (bought two of these, both for my kids. I still have them, but they are doorstops now). Macintosh iBook (the same one I just traded). In that same period I also bought the Dell PC I am typing this on, so since the PowerPC dual boot, I've always had access to both Mac and PC. I also purchased two PC laptops, one for my wife, and one for my daughter on her graduation. So the conversion to PC in this house has been slow and painful. I don't want anyone to think I traded the iBook because I personally don't like the Mac, I am still a huge Mac fanatic and if I could justify it I would buy one of their latest core duo laptops and set it for dual boot Windows/Mac operation. I just can't justify it is all. So I traded my iBook because my son has outgrown his iMac and does not want a Macintosh, he wants a Windows based computer. But the end result has been that my house, for 22 years a Macintosh haven, has now become a Windows based house where everyone in the house now uses a Windows computer. The assimilation is complete.

Comments (5)

Cullen
I wonder if Vista will have any impact on Mac sales? I'm concerned with some of the compatability and privacy issues in Vista and have been considering a Mac switch in the future. I'm really just going to have to wait until someone I know gets a copy of Vista and I can sit down with it and see for myself.
qwerty182764
Did you see what they did with Windows XP 64-bit? Apparently they can't make anything backwards compatible, especially drivers. Is this new OS 64-bit as well? Will it have the same backwards compatibility issues? Gaaah. I hate Microsoft so much that I'll pay them $100/year average. (strange, isn't it?) It's really the only option though if you want up-to-date hardware and the widest software selection. Actually, that's a little odd - if Microsoft owns all the information, dlls, libraries, ect associated with all their products, why in the world couldn't they, in theory, make every new OS backwards compatible all the way back to pre-windows DOS? Can't this floating point operation issue be overcome with a little pre-processing?
CosmicConservative
qwerty: I work in the software industry and manage software development teams, and the difficulty of keeping code bases up to date for more than a few years is significant. The difficulty of maintaining backward compatibility eventually becomes a very ugly game of supporting the lowest common denominator and that restricts what you can do going forward. The best example of this is with graphics. The original computers did not have the concept of color graphics, much less the concept of multi-channel processing which includes built-in ray tracing, shading and texturization. To attempt to keep old DOS computers compatible would severely restrict the programmer's ability to improve an interface by using the much more sophisticated graphics available today, or else they would have to maintain multiple sets of graphics code in each program to support the older graphics formats. It's just not feasible. In fact it is this inability of Windows to completely shed its DOS foundations that is really the cause of a lot of Windows problems. They really should have "green fielded" it, like Apple did with OS X.
qwerty182764
Hmm. I meant having the older software run on the newer system, not attempting to make new software run on old systems. What would prevent a newer system from giving an old program all the inputs it needs, and taking all the outputs according to it's knowledge of how the environment it was designed for work? If you have pseudo-drivers or pseudo-OSes from previous eras that were "top-of-the-line" at the time they went out of style, couldn't you have the new OS just load the old conditions to feed the program from an internal library or something? Sort of like a library of emulators. What would have happened to the internet if everyone's html content was made "obsolete" by some new standard? Theres simply too much valuable software content that would be thrown away by crossing some kind of obsolescence barrier right now.
CosmicConservative
So the OS is just software itself, right? When you are writing the OS, if you have to support four different generations of graphics output, your code starts to look pretty ugly, and it becomes increasingly hard to manage. Most OS routines are in the OS because they are called so much by applications written on top of them. Every time you put a check on an OS call to say "what version of DrawWindow do you want? The old monochrome one? the CGA one? the VGA one? the XVGA?" etc.... those become code branches and decision points. When you are attempting to optimize code, those sorts of things start to kill your performance. And they would be everywhere. So after a while it simply doesn't make sense to keep all the different routines, even if you could. Another thing that particularly hampers OS development is the fact that because it is software, the tools you use to write it change over time. The original DOS routines were mostly written in 8086 assembler. That code simply won't run on modern Intel chips. Even if it would, nobody writes in 8086 assembler anymore so you couldn't hire people to maintain those routines. Most OS source code was converted to C back in the 80s and 90s. Apple actually wrote a huge chunk of their Mac OS in Pascal, then moved to C. Even within a language there are versions. My old C compiler on my old Mac won't even compile code that will run on a modern Mac, things have changed too much. So if all of that code had been OS code it would have had to have been converted (at time and materials cost) to the new language or new dialect of language. It just becomes logistically impossible to keep backward compatibility forever.