Nearly 25 Years Ago, IBM Helped Save Macintosh 236
dcblogs (1096431) writes "Apple and IBM, which just announced partnership to bring iOS and cloud services to enterprises, have helped each other before. IBM played a key role in turning the Macintosh into a successful hardware platform at a point when it — and the company itself — were struggling. Nearly 25 years ago, IBM was a part of an alliance that gave Apple access to PowerPC chips for Macintosh systems that were competitive, if not better performing in some benchmarks, than the processors Intel was producing at the time for Windows PCs. In 1991, Apple was looking for a RISC-based processor to replace the Motorola 68K it had been using in its Macintosh line. "The PCs of the era were definitely outperforming the Macintoshes that were based on the 68K," he said. "Apple was definitely behind the power, performance curve," said Nathan Brookwood, principal analyst at Insight 64. The PowerPC processor that emerged from that earlier pairing changed that. PowerPC processors were used in Macintoshes for more than a decade, until 2006, when Apple switched to Intel chips.
Pairing? (Score:5, Informative)
Apple was definitely behind the power, performance curve," said Nathan Brookwood, principal analyst at Insight 64. The PowerPC processor that emerged from that earlier pairing changed that
PowerPC was pushed by the AIM alliance: Apple, IBM, Motorola. The latter two developed and produced chips. Apple had some input. The goal was an ISA that made it easy to emulate both m68k and i386.
Re: (Score:2)
THE goal of PowerPC was not to make it easy to emulate 68K and x86. It wasn't even A goal.
The goal of PowerPC was performance parity with x86 at much smaller die sizes and therefore much lower cost. All non-x86 architectures of the era targeted better performance at the same die sizes and costs as x86. What was unique with PowerPC was to be cheaper, that's all.
Re: (Score:2)
THE goal of PowerPC was not to make it easy to emulate 68K and x86. It wasn't even A goal.
You might want to go back and read some press releases from the AIM alliance at that time. Or even look at the ISA: there are a lot of things in there that only make sense if you want to emulate m68k or x86. They were positioning PowerPC as a migration path from m68k and i386 systems and being able to emulate both at a reasonable speed was part of this strategy.
Re: (Score:2)
Or even look at the ISA: there are a lot of things in there that only make sense if you want to emulate m68k or x86.
That sounds pretty interesting? Do you happen to have a reference for further reading?
Re: (Score:2)
I don't see anything in the ISA that would help migration of 68k or 386. However there was stuff at a higher level that would have helped, not specific to those earlier systems but which would help emulation or porting in general. Ie, ability to swap endianness, memory management systems, and so on. Apple itself wrote an m68k emulation system that ran under PowerPC, so clearly it was one of their goals. However there's nothing obvious that I see that was specific for emulating those 2 chip families rath
Re: (Score:2)
>What was unique with PowerPC was to be cheaper, that's all.
And yet it never was.
OS/2 not Windows, and no VMS ... (Score:3)
... the kernels (as Microsoft hired David Cutler to bring the VMS kernel with him to create Windows NT ...
Wrong on two counts. Cutler had worked on VMS but he did not bring it with him. NT was written from scratch. Also, he was not brought on board to rewrite Windows, he was brought on board to rewrite OS/2. While IBM worked on 32-bit x86-specific OS/2 2, Microsoft would in parallel work on the CPU architecture portable OS/2 3, aka "NT OS/2". Microsoft and IBM "broke up" and NT OS/2 was renamed Windows NT.
PowerPC ran the Blizzard Games ... (Score:3)
Too bad the PowerPC machines *couldn't run the damn games* or the requisite MS Office suites for students and business people to use them.
They ran Warcraft, Starcraft, Diablo and World of Warcraft.
Re: (Score:2, Informative)
No, this is stupid, wasteful, unoptimized software that performs like feces compared to a platform optimized piece of software.
The whole myth I've heard about software portability most of my life has never bore fruit that didn't need tweaks for different platforms.
The whole notion in the first place was to expand programming to the masses by giving the appearance of the elimination of the need of specialists.
A good intention, to be sure, except for the specialists.
The problem was that a specialist with know
Re: (Score:2)
No, this is stupid, wasteful, unoptimized software that performs like feces compared to a platform optimized piece of software.
Eh? What are you on about?
Yeah, those hand tweaked 16bit binaries performed really well on the pipelined i486 processors of the time. Really extracted all the potential out of the advances that were taking the CPU industry by storm.
In case you missed, I was being sarcastic. "Platform optimised" (read DOS) programs held the industry back at least a decade, and it's only after we left the 16-bit sheckles^W^Wplatform optimized software behind that x86 based platforms started to reach parity with their RISC bas
Re: (Score:2)
I bet Google DOES use some moderate amount of assembly. I once worked for an audio-recognition company and we did indeed use about 100 lines of x64 assembly to perform the inner loop, which was some complex audio signal processing routine. Similar to an FFT.
This was easily 10x faster than the C version, which we had for reference purposes, even when using the Intel compiker with all optimizations turned on.
So, just because you never saw a Tapir in your life, does not mean they can't exist because their dick is longer than you can imagine.
Maybe you shouldn't have been using an AMD processor:
(Intel has been slammed for their compiler creating code that directs non-Intel CPUs to completely unoptimized code, not taking advantage of SSE, etc, even when present in the non-Intel processor)
http://www.agner.org/optimize/... [agner.org]
Section 2.3 of this:
http://download.intel.com/pres... [intel.com]
Re: (Score:2)
Except that when the platform changed, the applications needed to be rushed to be re-ported, and only re-optimized slowly. This happened a lot. Windows and Mac did not remain static, they changed greatly over the years. That hyper-optimized Windows 3.11 application was slow on Windows NT or vice versa, and migration to Win32 really hurt a lot of older Windows applications. This is what gave Microsoft an advantage much of the time, they knew in advance how the OS was changing and were the first to take a
Compilers lose to assembly language programmers (Score:2)
"Knowledge of how the hardware operates", "Things like CPU instruction set options, memory alignment, etc.", are the business of compilers and their creators.
Perhaps, but they fail at it. Game developers often **have to** make up for the deficiencies of compilers.
Compilers optimize code much much better than humans do.
Perhaps the average programmer, but those specializing in assembly language routinely beat the compilers. Assembly is merely less common today because of (1) cost and (2) CPUs are so overpowered for nearly all tasks we can live with less efficient compiler generated code.
Re: (Score:2)
"CPUs are so overpowered for nearly all tasks we can live with less efficient compiler generated code."
And this is why an OS needs 15GB of disk space, a game 40GB, and a word processor around what? 2-3 gig?
Meanwhile a C64 runs a full blown flight simulator in 38K...
Not many Mac games were designed to be portable (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:3, Interesting)
That is extremely wrong and revisionist. Wintel was fucking huge in 1991. If you bought a machine with an x86 chip it very likely came with Windows "free" even if you never started it. Windows was everywhere; most people just didn't happen to like it.
No, it was inferior to most other OSes, but it also crushed them all, too. Whether preloads count as "competition" or "not competing" was something plenty of people argued about back then. But from an installed-base PoV (i.e. how an app developer would look at the potential market for their apps) it unambiguously "completed" and won.
Also, MacOS was horrible in 1991. That was the one relatively-popular OS that Windows could nearly compete on merit with.
Gotta agree with you, there. It would be several more years before I ever saw anyone with MS Office, and a few years after that, before I had to have some way to read MS Office files. Fucking lusers, you tell em "save in a standard format," and the blank stare-backs were just priceless .. yet also very frustrating. It was almost like being trapped in the novel Catch-22, where you wanna laugh at the fuckwits and yet their actions also really mattered and were dooming everyone, so laughing just wasn't quite the right response. Dark, dark times. 1991 was bad, but not nearly that bad, yet.
NO, he is correct WINTEL was NOT big in 1991. In 1991 MS released Windows 3.0. Win 1.0 thru 2.1 were pretty crappy and the PC industry was leary of 3.0 and had not really jumped on it. IBM PC and PC juuior came standard with DOS 6. You would have to go purchase Window separately. It wasn't until 1992 when Win 3.1 and 3.11 came out that IBM and Compaq started shipping PC's with Windows on them. That is when the Intel based "PC Clones" ( HP, Packard Bell, Compaq, and a littel later Dell , Gateway, etc) start
Re: (Score:2)
In 1991, real computing was done on unix workstations running BSD (Sun 3/60 anyone?).
The PC market was a cess pit. The Macintosh was nice, but the OS was horribly unreliable.
Re: (Score:2)
Why would you keep a 486 CPU on its own - surely the whole system would be more use if you went to the trouble of keeping the rest of the documentation?
Re: (Score:3)
Re: (Score:2)
In 1991, Microsoft+Intel was big and dominant in the "small personal computer" market, ie, PC, Mac, Amiga, Atari, etc. However at this same time this was close to the height of the Unix workstation market and Intel was not competing there very strongly. Windows was so early that it was generally a joke until NT came out, and PCs of that year still shipped with DOS usually. There were some some low end workstations that used 386 but they weren't very popular.
Going with PowerPC was intended to be a leapfro
Re: (Score:2)
Also, MacOS was horrible in 1991. That was the one relatively-popular OS that Windows could nearly compete on merit with.
Ummm..... Windows 3.0 was a 16-bit DOS shell that was horribly buggy and lacked a lot of functionality most take for granted with a GUI OS. MacOS System 7 was out by then. A real 32-bit GUI OS that was easy to manage, lightweight and simple. It did its fair share of crashing but was a MUCH better OS than DOS/Win3.x. I was more of an Atari ST user in 1991 still... we converted to Macs a little later after we realized the TT030 was pretty much vaporware and underperforming when a few units finally did shi
Re: (Score:2)
MacOS definitely had its flaws, but as user of both since version 1.0 of both, I will take a Macintosh CS (current in 1991) running MacOS 6.8 or 7.0 ANYTIME over a Windows 3.11 386 machine.
Personally I would wait a year and a half for 1993 and get a Mac LC, then spring for a PDS card with 386 CPU.
Then you can run crappy Windows 2 or 3 natively to avoid the ignorant stares and comments by co-workers aged -5 to -15(*) who will run to post comments on slashdot, yet also be able to switch over to Mac OS to get real work done.
* No I can't believe kids making such comments today are more than 15 years old right now...
It is pretty hilarious however about all these kids complaining about MS Office.
Re: (Score:2)
MacOS was horrible, and so was DOS and Windows 3.x. Compared to the state of the art those systems were like school projects, they only succeeded in the professional world because of the applications. Everyone in the real world was going full steam ahead with Unix (Unix wars started around then).
Re: (Score:2)
MacOS was horrible, and so was DOS and Windows 3.x. Compared to the state of the art those systems were like school projects, they only succeeded in the professional world because of the applications. Everyone in the real world was going full steam ahead with Unix (Unix wars started around then).
I clearly remember the shock of finding SysV has won and all that BSD goodness was not a part of my work day. This was on Suns.
ps -e FFS!
Re: (Score:2)
MacOS was horrible, and so was DOS and Windows 3.x....Everyone in the real world was going full steam ahead with Unix (Unix wars started around then).
Nope, UNIX was never a factor on the desktop, even ca. 1991. If you had the $$$ to afford a UNIX workstation, you often also had a DOS/Win PC to get real work done. Mac OS wasn't half bad, especially version 6 and earlier. It was when they tried to tack on all the extra stuff in version 7 that it started to fail under its own weight. I feel old now...at my first job I had on my desk, a Mac running version System 6 and a DEC VAX terminal. I think Clinton had just been sworn in.
An old UNIX joke, "What does wo
Twice the performance, half the price ... (Score:2)
Apple was definitely behind the power, performance curve," said Nathan Brookwood, principal analyst at Insight 64. The PowerPC processor that emerged from that earlier pairing changed that
PowerPC was pushed by the AIM alliance: Apple, IBM, Motorola. The latter two developed and produced chips. Apple had some input. The goal was an ISA that made it easy to emulate both m68k and i386.
No. The goal was twice the performance at half the price of the x86.
Now Intel's CISC based x86 was certainly more difficult to work with in terms of improving performance but Intel was not exactly lacking in resources, human or financial. Even if it took 10x to improves CISC compared to RISC, Intel had the 10x. Intel pulled off friggin miracles with x86 performance, not one expected them to reach the clock rates they did.
It turned out that in general PowerPC had a 20% performance advantage over an x86
Re: (Score:2)
However Intel was able to achieve higher clock rates than PowerPC and maintain a general performance lead.
That's not quite true, IBM makes some very fast PPC's, they have a 5GHz one available. In fact, you can buy 3.2GHz PPC chips in every Wal-Mart. The problem being, that IBM didn't have those 3+GHz PPC's ready when Apple wanted them.
Re: (Score:2)
However Intel was able to achieve higher clock rates than PowerPC and maintain a general performance lead.
That's not quite true, IBM makes some very fast PPC's, they have a 5GHz one available. In fact, you can buy 3.2GHz PPC chips in every Wal-Mart. The problem being, that IBM didn't have those 3+GHz PPC's ready when Apple wanted them.
I was referring to the era of PowerPC based Macs and the motivation for Apple's ultimate switch to Intel. Plus the PowerPC is something a little different than the workstation class POWER cpus from IBM.
Re: (Score:2)
I don't think the ISA was a goal, because PowerPC was really just a subset of the POWER architecture that IBM currently had in their mainframes and servers.
In fact, after PowerPC was released, the minor changes to the ISA that were done were re-incorporated back into the POWER ISA to make POWER binary compatible w
Re: (Score:2)
I don't think the ISA was a goal, because PowerPC was really just a subset of the POWER architecture
Superset of a subset, to be precise. For example, PowerPC omitted the multiplier-quotient register, and multiply/divide instructions using it, that were in the POWER instruction set architecture, but added multiply and divide instructions that used the general-purpose registers.
that IBM currently had in their mainframes and servers.
Presumably meaning "RS/6000 workstations and servers"; the instruction set architecture in the mainframes was System/370 (or S/370 XA or ESA or whatever).
Re: (Score:2)
Apple was definitely behind the power, performance curve," said Nathan Brookwood, principal analyst at Insight 64. The PowerPC processor that emerged from that earlier pairing changed that
PowerPC was pushed by the AIM alliance: Apple, IBM, Motorola. The latter two developed and produced chips. Apple had some input. The goal was an ISA that made it easy to emulate both m68k and i386.
Can we then add that 10 years ago Apple almost went under until Microsoft bailed them out.
Another misleading headline (Score:5, Informative)
I was working very closely with Apple at the time, and unless everyone was being lied to, "IBM saved Macintosh" is a pretty serious mischaracterization. More like three companies working together to create a platform useful to all the contributors. Did IBM put more into it than the other AIM members? Probably. But they didn't do it out of the goodness of their hearts.
Re:Another misleading headline (Score:5, Funny)
Did IBM put more into it than the other AIM members? Probably. But they didn't do it out of the goodness of their hearts.
There exists a noble, altruistic corporation that roams the lands doing the good work.
Mythbusted
Good work NE Altruism (Score:5, Funny)
Re: (Score:3)
And Galapagos' turtles, too. Those were the prefered fresh meat of the whaling boats' sailors.
Re:Another misleading headline (Score:4, Interesting)
At that time, Apple had plenty of RISC choices, all of which had better floating point performance than x86 and better performance overall. They could have chosen Alpha for its performance or MIPS as MS had done with the NT reference platform. They could have chosen SPARC or 88K and had more direct involvement with the future of their processors. Instead, they bought into IBM's claim that they would take over the x86 with equal performance at lower cost and lower power and got saddled with Motorola's processor design ineptitude.
It's a gross mischaracterization to say that IBM helped save the Macintosh. IBM led Apple to make a poor strategic decision that they had to rectify a decade later.
Re: (Score:3)
No matter what CPU they had chosen, wouldn't they have had to migrate off it to x86 eventually? It's not like any of the alternatives like MIPS or Alpha have endured or kept up with Intel.
Maybe in hindsight they should have gone x86 off the bat but at the time RISC had a lot of hype and interest even from Microsoft.
Although a switch to MIPS instead of PowerPC might make one of my favorite alternative history stories, an Apple/SGI merger in the early 90s, more plausible as merging MacOS and IRIX would have
Re: (Score:2)
SPARC and POWER seem to be still kicking pretty hard for performance. Now, power consumption is another issue with those platforms, but I digress.
MIPS is still alive, they simply found a different market to target.
Re: (Score:2)
PowerPC had good performance for several years. When the 603 and 604 were around they had better performance than x86 did. The problems started when the Pentium Pro came out. Even then it was not manufactured in enough numbers to be a real issue. Then the Pentium II came out...
Re: (Score:2)
PowerPC had good performance for several years. When the 603 and 604 were around they had better performance than x86 did. The problems started when the Pentium Pro came out. Even then it was not manufactured in enough numbers to be a real issue. Then the Pentium II came out...
No, I think it was more the Pentium IV where Intel overtook Motorola. The PPC G4 design had started to hit up against clock speed walls, and couldn't scale the FSB up either. While Netburst was a disaster for performance/watt, it did scale clock speed wise and had a very fast FSB and memory subsystem, and while everyone else was hovering around the sub-2GHz mark, Intel got plenty of high clock frquency practice.
Once the Netburst FSB was moved to the P6 architecture in the form of the Pentium M, Intel had th
Benchmarks (Score:2)
if not better performing in some benchmarks
...some of which could perhaps be better described as"benchmarketing"
Really miss the 68k (Score:4, Insightful)
A much more elegant architecture than x86. Still have to give Intel credit their manufacturing prowess gave them the edge.
68k was a neglected platform (Score:2)
A much more elegant architecture than x86.
Elegance without performance is ultimately pointless. And the 68k platform seemed to be neglected by Motorola. I don't know if the problem was economic, technical or some other issue but Motorola was clearly falling behind the competition for whatever reason. The x86 architecture is ugly (to put it kindly) but it's generally good enough, fast enough, cheap enough and it benefits heavily from network effects. Plus Intel is without question the industry leader in manufacturing efficiency (including die si
Re: (Score:2)
Neglected? The Macs that I owned went from 68000 to 68020, 68030, 68040, and then to PowerPC. Motorola continued the 68k line with
http://en.wikipedia.org/wiki/M... [wikipedia.org]
but, this was eventually dropped in favor of the PPC line.
I always wondered about M68K. (Score:2)
It sure seems like the M68k architecture could have been pushed forward more. Yeah, it was CISC, not RISC, but it was a very clean CISC. Modern x86 chips are really RISC machines internally, they just have a bunch of translation from the CISC instruction set to the 'real' ISA inside. If nothing else, that approach could have worked for M68k, right? Probably better, since the basic M68k ISA isn't so crufty and ugly like x86.
Re: (Score:2)
the 68k platform seemed to be neglected by Motorola
Nobody really took up the 68060, there was no reason to continue the line. They used a 68k core for the first dragonball [washington.edu]s, though, which appeared in the Palm Pilot. But then they got access to PowerPC cores, and those became the basis of the later dragonballs. There was just no reason to keep 68k alive at that point.
Re: (Score:2)
The problem with this fixation on "performance" is that it was all effectively sabotaged by the bloat of operating systems at that time. The resources required weren't keeping pace with the cost of hardware. It became infeasible for most normal consumers to keep up with what things like OS/2 and Windows were demanding.
It doesn't matter how spiffy your 486 is if it is spending all of it's time swapping.
My own 486 had extremely dissappointing performance when compared to a even mere 68000 until RAM prices bec
RAM (Score:2)
True. I was astonished when I invested a decent chunk of change and bumped my 100MHz 486 from 16MB to 64MB of RAM. Multitasking actually became practical, especially running Mozilla alongside something else. Of course, the 68K Macs of the day weren't that much better at supporting 'a browser and something else'. The cooperative multitasking of the Mac OS helped
Re: (Score:2)
The early 2000s (and 1999) also saw fierce competition between AMD and Intel. This happened after AMD stole the performance crown from Intel with the release of the original Athlon, which likely pushed Intel to actually make some improvements.
This eventually lead to the Pentium M (and later Core) microarchitecture which Intel has been building upon for the last decade or so.
Re: (Score:2)
Intel has always been the absolute best in the world at semiconductor manufacturing. It's their lithography that has kept them in the game through various design missteps (and disasters).
much more elegant (Score:2)
I'd still rather have a good blaster at my side
Re: (Score:2)
Re: (Score:2)
Or maybe Intel picked up the ball and used the 68k (as their engineers wanted) for the original IBM PC.
Presumably you mean "IBM picked up the ball...".
Intel? They're the guys that make memory and strange CPUs for calculators, right?
No, at the time, they were the guys who make 8-bit and 16-bit computers used in a variety of applications; I'm not sure whether they were still making the 4004 or not.
They'd still be on Power if not for two things. (Score:2)
G5s ran too hot for notebooks. IBM's manufacturing capacity for Power/PPC cores outside its own servers and workstations was eaten up by Microsoft for its XBox line. Apple was waiting too much on inventory. They switched to Intel not because their chips were more powerful, but because their chips were more available and could be used more flexibly.
Re: (Score:2)
IBM's manufacturing capacity for Power/PPC cores outside its own servers and workstations was eaten up by Microsoft for its XBox line
You mean Sony with the PS3. The Xenon in the 360 is based on the Cell's PPE.
Re: (Score:2)
A Cell is a PPC core with extra coprocessors, and was the secret processor that caused delays for Apple that IBM couldn't explain. IIRC it was no secret what chip was going into the PS3 before launch. Again, IIRC, Microsoft forced IBM into a minimum delivery rate and wouldn't allow them to disclose to other chip customers where the capacity had gone.
Re: (Score:2)
Indeed. The PC was IBM's way to fill a top-to-bottom order without letting other vendors in at the desktop/workstation levels. That was about it.
68K vs x86 - Apple vs IBM PC (Score:2)
The original PC, in 1981 ran on the 8088 - an 8/16 bit hybrid chip. By the time the Mac was released in 1989, the 486 was the chip of choice for the IBM PC and, more importantly, the clones.
Apple had a history and relationship with Motorola with the 6502 used in its Apple I and II lineup. When the Mac was released, the 68000 was a superior chip to the 386. And, there was the Apple vs PC war going on which helped solidify the choice - Apple was distancing itself from PCs anyway possible.
The 68K was a super
Re: (Score:2)
The original PC, in 1981 ran on the 8088 - an 8/16 bit hybrid chip. By the time the Mac was released in 1989
Strange that the 1984 commercial was for Macintosh, which according to you was released 5 years later.
Re: (Score:2)
At 1989 486 did not exist, you mix them up with 286.
Re:Intel (Score:5, Interesting)
Errr, yeah, but they could have just used Intel chips like everyone else. Ultimately it would have given better performance, saved themselves a lot of pain in switch over, and put themselves ahead of the curve selling to people who wanted to dual boot. So did IBM save them or cripple them?
As a result, Apple had the more POWERful chips for many years. They avoided the Pentium debacle completely. Pentium M was the first sane chip that Intel produced, and Apple got in with the Core Duo - just when the whole world was screaming how for ahead AMD was, and just before Intel turned things around.
Re: (Score:2)
Nonsense. The 486, Pentium Pro, P2, and P3 were all fine. It was only the P4 diversion that was a disaster. The Pentium M was simply a return to the P3 architecture, it was not new.
Re: (Score:2)
The most telling thing about the whole story is that the last chips in the P3 line were beating the first entries in the P4 line at the same clock speed.
Re: (Score:2)
The 486, Pentium Pro, P2, and P3 were all fine. It was only the P4 diversion that was a disaster.
Timing is everything, of course. If the iMac had been built on Intel Apple probably would have had to stay with a P3 for cooling/heat/noise reasons. That might have worked technically (the P3 continued to do well against the P4 on benchmarks) but it would have been heavily marketed against by its competitors.
The iMac actually is what saved Apple because by offering industrial design and fashion instead of raw
Re: (Score:2)
Re: (Score:2)
Re:Intel (Score:5, Informative)
Spoken like someone who has no idea about the market at the time. The PowerPC was introduced in 1992, announced in 1991. At the time, Intel's flagship x86 part was the 486 but they were trying to kill the x86 line. They'd released the i860 (RISC, not x86-compatible) in 1989 and tech magazines were saying it would kill x86. Windows NT was originally written for the i860 and only later ported to x86, so even Windows looked like it might not be tied to x86 in the long term.
1992 saw the launch of the Alpha and MIPS R4K, and 1993 saw the SPARCv9 ISA. It didn't look like a 32-bit architecture that was hacked onto a legacy 16-bit ISA had much of a long-term future. IBM and Motorola were two of the biggest players in CPU manufacturing and they teamed up to produce something that would provide a migration path for m68k and i386 software. The PowerPC architecture was based on IBM's POWER architecture but extended to make it easy to emulate m68k and i386 at reasonable speeds. Microsoft was signed up to port Windows NT and it looked like you'd be able to run Windows and MacOS (the two most popular desktop operating systems) and possibly some of the other less-popular ones (most of which were m68k-based) on the same hardware. IBM and Motorola were both going to produce chips, so there was guaranteed to be competition, which would bring down prices, and they were soliciting other companies to produce implementations of the architecture. Within a few years, PowerPC would be faster and cheaper than x86 and would run more software. At least, that was the theory. It sounded quite plausible, but history didn't quite work out like that.
Re:Intel (Score:5, Interesting)
This is technically true. Windows NT was originally designed to be OS/2 version 3.0 and at first they targeted the i860 which never did well, so they changed to the MIPS platform. Prior to release Microsoft decided to make it their next Windows platform and the rest was history.
What made Windows NT unique at the time was the Hardware Abstraction Layer (HAL) that allowed Microsoft to target multiple processor platforms. At release, Windows NT supported i386 (called IA-32 at the time), Alpha, and MIPS.
Re: (Score:3)
This is technically true. Windows NT was originally designed to be OS/2 version 3.0 and at first they targeted the i860 which never did well, so they changed to the MIPS platform. Prior to release Microsoft decided to make it their next Windows platform and the rest was history.
What made Windows NT unique at the time was the Hardware Abstraction Layer (HAL) that allowed Microsoft to target multiple processor platforms. At release, Windows NT supported i386 (called IA-32 at the time), Alpha, and MIPS.
And later, it ran on PowerPC.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
So please elaborate where is the hardware support in PowerPC to emulate 68k and x86.
Good luck.
Apple got some good emulation software but it had zilch to do with PowerPC being designed with emulation of those architectures as a goal.
Re:Intel (Score:5, Interesting)
Re: (Score:2)
PowerPC can run in mixed, big and little endian.
Which is pretty important if you want to emulate either, as x86 and 68k have opposite endianess.
Re: (Score:3)
You left out OS/2, which Lou Gerstner hadn't given up on yet (although the nightmare of the PPC port helped him make up his mind). IBM at this point still had hopes of re-conquering the desktop market, and the CHRP (Common Hardware Reference Platform, aka PPC
Re: (Score:2)
Re: (Score:2)
I believe that x86 emulation existed for IRIX on MIPS and Solaris on SPARC (and maybe more, just the two I know) via SoftPC.
Re: (Score:2)
One feature of the 68k to PowerPC transition was that they had software emulation for the 68k. The PowerPC was able to emulate the 68k sufficiently that most software would still run on the new hardware. This emulation was good enough that most applications performed on par with the older native platforms.
The 110 MHz PowerPC was at the time the fastest machine for running 68K code. At the time there were actually Atari users who bought a PowerPC Mac + Atari emulator because it was the fastest Atari computer that you could buy for any money.
Re: (Score:2)
Which is why Apple left the file system and network stack running in emulated code until they were shamed into fixing it?
Re:Intel (Score:4, Interesting)
At the time, PowerPC chips were more powerful than x86 in terms of raw computing power. I believe that the G5 Mac was technically classified as a supercomputer based on an old standard of flops and could not be exported until the US government updated the definitions.
The reason for the switchover to x86 had to do more with power efficiency, customization, and logistics. While the PowerPC architecture did lend itself to better overall computing performance, it was lacking in power efficiency and heat. For a desktop that's not a major problem, but it is a problem for laptops. It's a problem that IBM never really solved as they never released a mobile G5 and Apple was stuck with mobile G4s until the Intel switchover. Here is one area where Intel was way ahead.
The two other related issues have to do with Apple's needs and IBM and Motorola's manufacturing logistics. Apple despite ordering millions of chips a year was always going to be a small customer in terms of volume. However Apple was going to need a heavily customized consumer PowerPC chip that required to be updated almost every year. Meanwhile most other PowerPC customers would want server/workstation chips that IBM used in their own products. Now these can be done but these factors cost time and money. I can see why Motorola and IBM (and also Apple) would be less likely to invest into new chips.
On the flipside, the Xbox 360's Xenon processor would be more the model of what IBM/Motorola wanted. Although it was heavily customized, the basic design has not changed in 8 years when the Xbox One was launched with estimated sales of 40+ million. This gave IBM enough time to do a die shrink to cut costs.
The change to Intel gave Apple many advantages. First of all, faster and more efficient mobile processors were available. Second, most of the features that Apple wanted were already in the x86 design as they were designed for consumer PCs. Third, any customization Apple requested from Intel, Intel could sell to competitors like Dell. For example, the first MacBook Airs used customized Intel Core processors in which the chip package had been shrunk 40%. Intel didn't mind investing the money for this customization as they sold them immediately to other customers. Many of the features that Intel got in the collaboration became part of the Ultrabook specification.
Re: (Score:2)
At the time the PPC was faster at integer math, the x86 faster at floating point.
There were many pissing contests on /.
Re: (Score:2)
It was the G4 and a considerable level of creativity in Apple's marketing department. They were not considered a "supercomputer". They were briefly subject to an export ban to some markets because they breached a arbitrary limit that had already changed by the time they hit the market.
See, for example:
The extend of their superiority over the Intel and AMD processors of the time also need to be taken with a grain of salt. As with most Apple touted benchmarks, the fine print would reveal that the "up to t
Re: (Score:3)
Right, so this is the infamous mac os 7 era right? Powermacs? Where motorola code was emulated to work on PPC? Apple being led by non-jobs? When Macs didnt just needed a restart every 24 hours (like windows did) but would outright ruin there system install every other week?
That was the most shitty Apple period ever.
Yeah, I supported macs for an ISP back in the day. Saw many sad mac icons.
Re: (Score:3)
Re: (Score:2)
Re:PPC macs were awful (Score:4, Interesting)
Actually, I was surprised how solid Mac OS 8 was after going through Mac OS 7 and the trials and tribulations of unimplemented trap errors (hallmarks of 68K emulation). As long as you didn't have to go crazy on extensions, you could expect your Mac to keep on working. It didn't have any of the conveniences we have now with OS X, but it was far better than most of the Windows experience at the time (remember Plug and Pray?).
Besides, if you were really serious about running a server with Mac hardware, you loaded up MkLinux or bastardized AUX implementation. Hell, there was even a Mach kernel implementation for Mac hardware. And as you got further along into PPC architecture, you selection of Linux became even better (Yellow Dog was a favorite of mine). Apple's closed architecture made it fairly easy to target device drivers for almost all the peripherals. And the early adoption of USB made it easier as well.
Re: (Score:3)
Macs made USB!
It was very late in coming to Windows, and early implementations on Microsoft was horrible. They almost did the same thing to Firewire, and killed off the floppy long before it happened on PCs. SCSI implementation on Mac was also better. Mac tend to lead, PCs tend to "me too".
I have a theory on why this is, and it goes ... something like this.
Apple looks towards the future, and builds what will be "standard" in 3 years with their top of the line products. Things like USB, SCSI, Firewire, No Fl
Re: (Score:2)
They also made WiFi. I had it in my 1998 iMac. But I had to wait years until my PC neighbours would follow suit and stop laying cables all throughout the dorm.
Re: (Score:3)
Macs didn't "make USB", they forced it on their users while giving a big "fuck you" to all of their old customers running anything else. It's not like the old stuff was horrible either (ADB, SCSI).
It was a little annoying that Apple made the jump all at once into USB, but really - a couple of RS422 ports was better? ADB was always only for mice and keyboards, and years of experience showed that for most users, SCSI was just too expensive and hard to set up. Or don't you remember "SCSI Hell"? For higher end Macs, you could retrofit SCSI, serial, and even USB cards if you really needed to. Some configurations even included a SCSI card.
As far as "USB was everywhere on PC's" that's just wrong. At the tim
Re: (Score:2)
Macs didn't "make USB", they forced it on their users while giving a big "fuck you" to all of their old customers running anything else. It's not like the old stuff was horrible either (ADB, SCSI).
The move to USB was a practical matter. One interface for low bandwidth connections: USB. One for high bandwidth ones: FireWire. It was about future proofing than legacy. And it had the effect that it brought down costs when you could use the same peripherals for Mac and PC if the drivers were there.
In the meantime, USB was everywhere on PCs. It just wasn't forced down everyone's throats. Even recent systems with USB3 quietly included will still include interfaces from the :"dark ages".
It also wasn't well supported until way after Apple made their change. Oh it was there. But adoption was poor. Drivers were non-existent or poor. Even Windows didn't have proper USB support til Windows 9
Re: (Score:2)
Re: (Score:2)
Besides, if you were really serious about running a server with Mac hardware, you loaded up MkLinux or bastardized AUX implementation. Hell, there was even a Mach kernel implementation for Mac hardware.
...which was what MkLinux ran atop ("Mk" for "microkernel", although how micro the Mach kernel is could be considered a "topic for discussion").
Re: (Score:3)
Right, so this is the infamous mac os 7 era right? Powermacs? Where motorola code was emulated to work on PPC? Apple being led by non-jobs? When Macs didnt just needed a restart every 24 hours (like windows did) but would outright ruin there system install every other week? That was the most shitty Apple period ever.
The emulator was key in allowing users to use older 68k apps on the new PowerPC chips, until the software houses released versions built for the PowerPC. A lot of companies (including Apple itself) hurt the platform by delaying their PowerPC update releases. The OS did have some issues; I'm not going to sugar coat it. Apple also took a few journeys down dark alleys with poorly designed hardware during the '90s. Of course the alternative at the time was Windows 3.1, which wasn't a utopian dream either.
Re: (Score:2)
And yet, at the same time, the vast majority of PCs were still using DOS, because Windows was a fucking joke and all the software that ran in Windows was over-bloated garbage.
News flash: All PC options in 1993 sucked.
Re: (Score:2)
News flash: All PC options in 1993 sucked.
Ah, but what about the Amiga?
[Guru Meditation]
Re:PPC macs were awful (Score:4, Informative)
Right, so this is the infamous mac os 7 era right? Powermacs? Where motorola code was emulated to work on PPC? Apple being led by non-jobs? When Macs didnt just needed a restart every 24 hours (like windows did) but would outright ruin there system install every other week?
That was the most shitty Apple period ever.
Windows NT 4.0 never needed a restart every 24 hours, desktop systems maybe. If you had Windows NT servers that needed reboots that often, then you simply had bad Windows NT admins who didn't know how to resolve device driver, memory, or disk issues.
Re: (Score:2)
Wait, there are updates for Windows?
Uh-oh.
Re: (Score:2)
I'd suggest it was ARM more than IBM that saved Apple
The Newton saved Apple? (Remember, this isn't about today, it's about 25 years ago.)