A History of Commodore’s 8-bit Computers
lowendmac.com
lowendmac.com
The C64 is a classic case of a company not falling prey to the innovators' dilemma. They built the C64 when they already had one of the most successful computers on the market in the VIC-20. Tramiel had shown an uncanny knack for spotting evolution in the market on multiple previous occasions and leapt from one profitable business to another, leveraging the success of the earlier to fund the latter.
And, then, the faltering began. Instead of once again shooting for a big hairy audacious goal (64k for $595, in the case of the C64), they cut corners and delivered less power for more money (C16 and Plus/4, both massive market failures, because people aren't idiots). The article doesn't cover it, but the Plus/4 was extremely weak for games, compared to the C64. Despite having support for more colors, it didn't have hardware sprites and sound was a regression to the old bleep bloops of lesser computers, compared to C64's beautiful and powerful (for the time) 3 voice synthesizer chip (designed by the dude who went on to found Ensoniq, a leading sampler/synth company of the 80s).
The SX64 is less clear cut of a mistake...it was a beautiful machine, built well, and competitive with other portables of the time. Not sure why it did so poorly. I guess the business market wasn't into the Commodore brand by that time, and it was the only market that could afford it. I remember seeing "Name Brand Computer!" closeout special ads in the various computer mags at the time, and it was clearly an SX64...I remember wanting one, too, but couldn't afford it even at the drastically reduced prices. I still don't know how to interpret it in the history of CBM. Marketing failure? Poor market fit? Just too expensive?
It took them years to bring out a C64 upgrade in the C128, which was a modest success. I think part of the reason it wasn't a bigger success was its high cost (both for CBM to build and consumers to buy). The Z80 chip was a boondoggle bolted onto the side of the design that nobody used. Again, failure to achieve any meaningful hold in the business world meant there was no C/PM usage on C128 to speak of, and it was wasted effort and cost to try to tackle it.
The dedicated game machines are also a failure blip on the radar, and I think it's clear why: They reduced the utility of the thing, delivering less value, at a slightly lower price point; trying to boost margins at the expense of customers was a mistake they'd make over and over. The cost-cutting instinct at CBM was strong, but not in the direction it needed to go...people want more value for less money. They never want less value for less money. I don't know how to express this truism, and I don't remember where I've read studies about it, but people don't readily accept downgrades like this, and Commodore introduced these kinds of downgrades constantly, and it's an explanation for almost every one of their big failures, and when they went against that grain (and delivered more value for similar money, they had big hits).
Other later examples...the Amiga 500 was effectively an Amiga 1000 for half the price. Sure, smaller case, but it was just as capable of a computer. And, it was the most successful Amiga model, by far. Had CBM always followed this model of delivering more for less, without pursuing all the stupid side projects that were clearly bound for failure, they would still be around today (though Gould may have even been able to kill that successful of a company).
Even as a kid, I could see that the C16 and Plus/4 were bound to fail. They were utter shit for games, and games were the primary reason families were choosing C64 over other low cost options. Likewise, one could see that the C128 was going to struggle because it cost a lot to produce and had features that weren't going to be used (I never saw any C/PM software for C128, and I was using a C128 and then C128D until I got an Amiga in 1991...I was a hardcore user), and yet they kept shipping out that goofy hybrid concept for all those years (that's why the C64 kept going longer than the C128...it was simply cheaper to make and cheaper to buy, and still provided pretty similar value to the 128, because so little software for 128 existed).
Likewise, Amiga got the chopshop treatment on a few occasions, where they tried to make gaming versions and home entertainment versions. Always too little value, given competitors of the time, including compared to the Amiga itself. All trying to goose margins, without delivering more value.
Almost shocking consider its deficiencies and being sandwhiched between the C64 and Amiga for most of its existence.
Tramiel had kept Commodore constantly moving at breakneck speed with very little room for error by cutting prices so aggressively there was next to no margin. It was actually one of his price cuts that caused him to get pushed out, as well as savage Comodores retailer network (they had tons of hardware in the pipeline, announced a massive cost cut and refused to reimburse or credit retailers for the difference in recommended retail price, causing lots of retailers to lose lots of money, many of whom subsequently dropped Commodore).
But the C64C went the opposite direction: Despite 8-bit machines being past their prime at the time, the C64C was launched at a higher price point, often obscured by bundled that included GEOS and/or Quantum Link. At the same time it was drastically cost reduced. Some of it is obvious - if you open an early C64 vs a C64C the case seems pretty much empty in the latter; the 8x8KB RAM chips are replaced by one or two; lots and lots of 74xx series chips are replaced by a couple of custom asics etc. Some are not so obvious - fewer different types of screws etc.
The result was that the C64C was a large part of saving Commodore at a very difficult time (when was Commodore not in crisis?) by dramatically increasing Commodores margins. Probably the first and only time that Commodore had margins similar to Apple, though still at a much lower price point.
Of course, shortly after essentially saving the company from one of its worst crises ever, Rattigan was fired by Irving Gould, and Gould personally took over as CEO - allegedly because Gould was annoyed that Rattigan got lots of positive PR. Rattigan later won a $9m lawsuit against Commodore over the firing... The history of Commodore management is that success was as bad for your continued employment as failure.
The Digital Antiquarian has more fascinating details on Rattigan's role at Commodore [1]. In this telling, he comes off as not-so-bad, actually pretty competent, but ultimately foiled by the egos of the executive board.
[1] http://www.filfre.net/2015/11/the-68000-wars-part-4-rock-lob...
You could see that with how HP was flip flopping around as the board was brining in new CEOs ever so often because the share value was lagging.
Or now just as Nokia seemed to be coming back around the board brought in Elop...
Anyway, a few stories about Commodore's history were imprinted on me thanks to this book, and I'm going to repeat them here from memory.
One: The PET's launch was filled with problems. Commodore originally wanted a guaranteed retail channel, so when they first started developing the PET, they approached Tandy about a partnership where Commodore would make the computer and Tandy would sell it. Tandy politely declined Commodore's offer... because Commodore sold them on the idea making of a home computer so well that Tandy decided they should both make and sell their own computer, cutting Commodore out of the loop and resulting in the TRS-80. The PET's development was filled with delays, and by the time it actually launched, the TRS-80 has beaten it to market. It was already obsolete by the time it came out, and then IIRC they had problems introducing the floppy drive as well, with its launch plagued by delays and mechanical problems. When Commodore began work on the VIC-20, they weren't so much following up a successful product with a next generation as they were desperately trying to make up for the PET's problems.
Two: With the VIC, Commodore found out that naming a computer was harder than it looks, especially when you're trying for an international launch. They originally wanted to name it the Vixen to promote it as sleek and sexy, but the name ended up being too sexy for the European market since "Vixen" is pronounced like Wichsen, which is German for "masturbation". So they shortened it to Vic. Unfortunately, they discovered that a German would pronounce it like Fick, which means "fuck". Ultimately, they decided to go with different names for different markets: they named it VIC-20 in the US and VC-20 (short for "VolksComputer") in Europe. On a similar note, the medicine company Vicks had the same problem, so they chose to spell their name as Wicks in Germany.
I became an embedded computing guy later on... :)
gladly -as i found out in the first dotcom bubble - that not much has changed. ok, everything has changed, but "writing programs" was still "writing programs" and it wasn't that much of a jump from BASIC to "that stupid subset of PERL that the template engine of that long gone agency used".
we should bring back that "printed code" magazines. i mean really just a magazine where there is pure code and only a short discussion about it. not that patronizing how-to shit thats currently available.
To this day, even though I touch-type most of the time, I can still type quickly with one hand, while the other hand is used to keep my place on a printed document I'm transcribing. (Not that I do that much anymore.)
I think GitHub and the like have filled that space pretty well.
As a typical nerdy kid interested in sci-fi, robots, and computers, I was immediately obsessed. The guy who sold us the computer must have been into the BBS scene at the time because he included a box of 20-30 floppies labelled with hand-printed stickers and loaded up with all kinds of weird software with cool music and graphics when you started them up. I'd later learn that this was my unwitting introduction to crack intros and pirated software.
Since few of these disks were "official", there was only documentation for a handful of programs. I spent the next couple of years slowly discovering and experimenting with all of the programs on these disks as I tried to figure out what they all were. Some were clearly games and some seemed opaque at first but later became an obsession (Zork and several other Infocom titles).
The package also included the big book o' Commodore BASIC commands that was included with the retail machine. Between that, BASIC programs from magazines, and figuring out how to LIST a loaded BASIC program, I spent the next several years teaching myself the, er, basics and occasionally trying to "hack" some of the games to give myself way more gold/health/experience by changing different values or POKEing inappropriate numbers in shameful places.
Unfortunately, even though I spent hours in that unique ADHD realm known as hyperfocus, writing programs that drew pictures, played music, or simulated an interactive chat (really not that cool, just picking numbers that corresponded to your reply and following a path, choose-your-own-adventure style), my folks also told me to spend less time on the computer. I distinctly recall my well-intentioned stepmother telling me I didn't want to become "a computer nerd".
I don't know if they realized how lucrative that stuff could've become had I stuck with it. Either way, as I got older, barring a brief unit on BASIC in a high school computer class (which I aced since I'd pretty much learned it all in grade school), I lost track of programming. I've tried learning more modern languages since then but for whatever reason, the willpower and interest needed to sit down and code just isn't with me anymore.
Maybe it's the sense of discovery that's missing in lessons. I still enjoy learning new software when I need it to accomplish a particular task so maybe I need to leverage that if I want to really get back into programming, even as a hobbyist. Learning to use a tool in order to accomplish a particular task is a lot more engaging that learning to use a tool just to learn it.
Either way, I credit my early experiences with that Commodore for my continuing love of computers and using them to do fun and interesting things. I may not be a programmer but I'm not afraid to read documentation and learn how things work. I love trying out new features or discovering old ones. My interest in that old SID chip music taught me about MIDI and the C128's graphic commands evolved into my current hobby of creating and displaying digital art and interactive graphics.
We kept that C128 as our sole home computer until we eventually got a cheap 386 somewhere in the mid/late 1990's. Never did get that Amiga I wanted but for me, Commodore is the root of my tech-nostalgia and the starting point for many of my current interests and skills.
http://www.amazon.com/Commodore-Company-Edge-Brian-Bagnall/d...
The second edition is substantially extended and has been split in two and only the first volume has been released yet (the second volume is finaly close to finished, thanks to a Kickstarter).
Wasn't Broderick's character using an IMSAI to show he didn't have the money for new hardware, and had to make do with 2nd hand stuff?
'War Games' isn't a half bad game on the C64, either!
The contest was, if I recall correctly, tied to the movie. Like, win a computer "like" the one Matthew used in the movie War Games.... or something along those lines.
My friend and I took home a stack of those forms and filled out at least 100 (probably more) but we didn't win.
Fun & memorable times. Thanks for the info on the IMSAI.
Still, one of the first programs I wrote for that Commodore was a way to trick my younger brothers into thinking I'd somehow "hacked" into some generic military computer system. It was just a bunch of text menus where you input the number of the option you wanted and "navigated" this alleged remote computer. I even used some time delay routine in the output so the text wasn't displayed all at once, but rather "typed" out one letter at a time so it looked like info being received over a network connection.
Pretty sure it ended with accidentally triggering nukes or something ridiculous and I doubt I was fooling even my little brothers but it was a fun idea. My concept of the underlying tech and military networks was rudimentary in the 5th grade to say the least.
In addition, moderators review the vouched-for comments and in many cases have unbanned accounts that didn't need to stay banned.
amyjess's comment was killed by a spam filter. Users vouched for it, so it was unkilled by the time we saw it.