Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

gpat

macrumors 68000
Mar 1, 2011
1,928
5,339
Italy
The real smash was making the iPod usable with Windows/PCs too. Back in 2005 or so, many people I knew had an iPod, but nobody I knew had a Mac.

The guy really had a problem with occasionally getting sucked into his own reality distortion field.
There was no way the iPod could have succeeded if it stayed as a Mac-only, FireWire-only accessory.
Luckily he had opportunities to fix those kind of mistakes soon enough.
 
Today we remember Steve for killing the Mac clone market, but Apple was in such bad shape in 1998, and IBM/Motorola would continue to screw him so many times over, that it could've gone either way, really.

In defence of Motorola and IBM here, there was this peksy little thing from 1990 called the AIM Alliance.

In such a joining of corporate forces, every party are equal partners, even if what each partner brings differs. Steve’s returning to Apple showed signs of halting/blowing up Apple’s end of the alliance, putting a kibosh on PowerPC manufacturing for clones and reducing the PowerPC chip sales to a functionally single customer base (until Motorola started looking at the embedded market to recoup some of those investment costs for co-development with IBM, and IBM went ahead with their own POWER line).
 
  • Like
Reactions: TheShortTimer

Analog Kid

macrumors G3
Mar 4, 2003
9,351
12,580
That was kind of an avoidable product, I wonder what made him do that considering how bitter he had become towards Motorola for a very long time by then.

These kinds of projects can take years to deliver. At the time, access to iTunes may have been seen as an incentive to get Motorola to step up their game, and by the time it was completed Jobs knew Motorola was no longer their chose processor and the iPhone development was going to make ROKR look like a joke. Contractual agreements probably prevented Apple pulling out.
 

rampancy

macrumors 6502a
Jul 22, 2002
741
999
Freescale did have some interesting things coming with their e600 technology. The MPC8641D was a dual core CPU with a FSB running at half the CPU clock speed (same as the G5) finally shaking that 167MHz BUS that just hung on too long. Their dual core 1.5GHz CPU with a 768MHz FSB would have been an interesting comparison to the Core Duo. Since the G5 already had dual core 970MP from IBM, if Apple had liked what Freescale was doing, I think there is a chance the Intel switch might have been delayed, or maybe never happened.

The thing about the e600-derived PPC CPUs is that they were still based off of the original core of the G4. Even with an enhanced processor bus and a second core, would it have been able to be competitive with a Core Duo? Perhaps in 2006, but would it have been able to stay competitive with the Core 2 Duo and the subsequent Core iX series? I highly doubt it. Not with Freescale pivoting the e600 core towards the embedded market, a market that would be far, far more profitable for them to pursue vs. Apple's share of the desktop market.

And that's assuming Freescale could produce a CPU like the MPC8641D at the scale Apple would have wanted, on Apple's timeframe, at the price it would have wanted them (it's always been my impression that price was the reason why Apple balked on the 7448). At this time, Project Marklar would have been able to demonstrate real results running OS X with Rosetta on x86 hardware.

And maybe I'm wrong since I don't know the details, but would the TDP and performance per watt of Freescale's post-7448 CPUs have enabled them to be put in a machine like the MacBook Air, or offer G5-level performance in a PowerBook? Recalling the original 2005 Keynote, it was clear that Apple wasn't interested in what was competitive now, but what Intel was going to have in its roadmap down the line.

It would have taken a lot on the part of PPC development to delay or even prevent the x86 switch from happening: On IBM's part, they would have had to have the financial incentive and technical chops to focus on significantly reducing the G5's power consumption and heat output, while continuing to boost performance – at least enough to make a PowerBook G5 viable and make good on Jobs' boast of hitting 3 Ghz in the PMG5. Perhaps with more money and resources it would have been possible, but it would happen soon enough to address the growing performance gap between the PowerBook and Wintel laptops? On Freescale's part they would have had to do the same to make a potential "PowerBook Air" not just viable, but competitive too.

And not just that, but they would have had to have a development path that would deliver CPUs competitive with Intel's roadmap. Given what we've seen from Motorola Semiconductor/Freescale, I wouldn't have had any confidence in that happening (even if we don't count rumored promised-but-never-delivered CPUs like the fabled 7457-RM and the infamous 7500).
 
Last edited:
The thing about the e600-derived PPC CPUs is that they were still based off of the original core of the G4. Even with an enhanced processor bus and a second core, would it have been able to be competitive with a Core Duo?

This’ll be a response in three parts. :)

Owing to Freescale’s own work on improving the architecture, one can look to the 1.5GHz Core Solo in the Mac mini, versus the 1.67 GHz in the 7447. Were the e600/PPC8641/PPC8641D to have gone anywhere on the Mac, the previous — Cole Solo versus 7448 — can’t really be compared in terms of performance and time of release, as the e600 would have been the most advanced 32-bit consumer-level offering at the time the Core Solo/Duos reached market.

That said, it is somewhat surprising no one ever tinkered with a PPC8641D (the “D” for “dual”, allegedly consuming less than 25W at 1.5GHz) in a non-embedded use-application and ran Geekbench on it (ostensibly either in Linux or BSD). That would have been something worth seeing.

Perhaps in 2006, but would it have been able to stay competitive with the Core 2 Duo and the subsequent Core iX series?

Here’s part two. :)

This is sort of an impossible question to answer, owing to how research development sputtered after the PowerPC’s principal customer bailed out. We also know PA Semi found new inroads with multicore PowerPC architecture, including 64-bit applications, but the principl customer to bail on PowerPC cosplayed a corporate amoeba and devoured PA Semi, leaving us with cryptographically locked/“paired” iPhones/iPads. :p

Between Apple crashing the AIM Alliance singlehandedly and Apple halting continuing development of PowerPC architecture by any serious start-up it could afford to swallow whole, the entire R&D to have have come to pass is, frankly, unknowable to any of us. But we can fathom a different Apple which showed a different kind of shrewdness (maybe in another multiverse), in which Apple continued with PowerPC development and PowerPC products, working truly in alliance with Motorola and IBM, whilst at the same time also selling a separate line of Intel based systems running the exact same OS. This would have put a lot of heat on Microsoft, as neither of them were developing an OS for PowerPC systems (that anyone is aware of, at least).

But then you had Steve, who we know to have had a vindictiveness when anything didn’t go entirely his way (witness: Motorola, 3GHz, ZFS, an obsession with hardware products not being user-serviceable, etc.). —_—


I highly doubt it. Not with Freescale pivoting the e600 core towards the embedded market, a market that would be far, far more profitable for them to pursue vs. Apple's share of the desktop market.

And for part three:

Freescale recognized there was an immediate need to be fulfilled in the embedded market (such as in vehicles and fabrication/automation), and that pivot was responsive in the face of losing a major customer from a business alliance (one already hobbled by Steve after banning Mac clones with the launch of the PPC 740 in 1997) — an alliance which no longer existed (because, again, Steve). The e600 was adapted for customers which needed the processing power for their embedded needs, from a company with a lot of chops already under their belt. A best-case business outcome for Freescale would have been to the means to sell to Apple and third-party clones, as well as the embedded market. That, of course, never came to pass.

And that's assuming Freescale could produce a CPU like the MPC8641D at the scale Apple would have wanted, on Apple's timeframe, at the price it would have wanted them (it's always been my impression that price was the reason why Apple balked on the 7448).

A bit ironic, once one considers how much of a retail pricing premium Macs commanded, even then, over their i386/x64 counterparts. As for the 7448, I’m not sure how this would have been a substantially more expensive CPU, owing to its refinement of an existing line which Apple had been using for roughly three years (or whenever the 7455 went on sale).

Apple’s time frame was, from the hindsight of it, a matter of saving face after Steve put unrealistic pressure on the 3GHz performance benchmark, before pivoting completely once having announced the Intel transition (some 18 years ago today). Steve was shrewd and frequently smart, but he was also impressively woodenheaded, often arrogant, and not entirely the near-term visionary I’m guessing he believed in his own headcanon he was.

And maybe I'm wrong since I don't know the details, but would the TDP and performance per watt of Freescale's post-7448 CPUs have enabled them to be put in a machine like the MacBook Air, or offer G5-level performance in a PowerBook? Recalling the original 2005 Keynote, it was clear that Apple wasn't interested in what was competitive now, but what Intel was going to have in its roadmap down the line.

Like you, I lack all the back-end stuff not privy to the public. But considering the way Motorola/Freescale developed the 8641D to function at rated clock speed, as roughly 25W (whether that’s TDP, or a sitting average, I honestly don’t know), coupled with PA Semi’s own development, the lower-power, multicore, and 64-bit tech was coming on line. It just wasn’t coming online by one, single, simple juggernaut wearing blue (the other blue).

It would have taken a lot on the part of PPC development to delay or even prevent the x86 switch from happening: On IBM's part, they would have had to have the financial incentive and technical chops to focus on significantly reducing the G5's power consumption and heat output, while continuing to boost performance – at least enough to make a PowerBook G5 viable and make good on Jobs' boast of hitting 3 Ghz in the PMG5.

The “G5” was never gonna make fetch happen on portables. IBM never designed the 970 for that use-case. This was Steve’s folly in picking favourites in the disintegrating AIM Alliance: that was a strategic gaffe in the pursuit of a tactical win.

The AIM Alliance really was remarkable, even as Steve had no love for it (again, woodenheadedness, arrogance, farsightedness, etc.). He could have nurtured it when he was brought back aboard, but for whatever reason in his own mind, he chose not to. And maybe it derives from the same reason why he, with NeXT, ditched Motorola in favour of a NeXTSTEP which would run on Intel/i386 hardware: the hardware product mattered less to him than the software (and the technical ability to engineer control over that software, even if he wouldn’t be alive to see that come fully to pass).

Perhaps with more money and resources it would have been possible, but it would happen soon enough to address the growing performance gap between the PowerBook and Wintel laptops? On Freescale's part they would have had to do the same to make a potential "PowerBook Air" not just viable, but competitive too.

We knew Apple had been running OS X on both PPC and Intel architectures from the outset (no doubt a carryover from NeXTSTEP 3.3), and Apple could have completely supported running OS X on two major hardware platforms — one RISC, one MIPS, and putting the pressure on Microsoft. Then again, there just as well might have been a “““gentelmen’s agreement”” between Steve and Bill, when Bill threw nine figures at Apple in 1997, that Apple wouldn’t run OS X on multiple hardware platforms simultaneously.

We, the consumer, lost some choice in that arena, as OS X on either major platform had different customer bases with different specialist needs: customers with professional and semipro-level hardware and software developed by and for PowerPC/RISC gear (think MOTU and a whole slew of music and video production gear developed and made available over the previous dozen years); and customers with bog-standard Intel/MIPS boxes who needed to connect online, print to the department printer, and to tap into using scientific hardware designed only for Intel/AMD systems running Windows (which an Intel Mac could also do natively). We know Rosetta made on-the-fly code translation possible, as it was needed. Rosetta could, in theory, work in both directions. Apple, under Steve, chose to merge those two customer bases as we came to know.

And not just that, but they would have had to have a development path that would deliver CPUs competitive with Intel's roadmap. Given what we've seen from Motorola Semiconductor/Freescale, I wouldn't have had any confidence in that happening (even if we don't count rumored promised-but-never-delivered CPUs like the fabled 7457-RM and the infamous 7500).

Intel’s road map was simpler, because only one vendor/company was involved. The PPC roadmap was, meanwhile, divvied by as many as three different companies (Freescale, IBM, and PA Semi, with the latter, barely two years old, still teething in 2005).

Simplest won out, for worse or better. And once more, even more simple — by keeping it all internal — likely factored into Apple’s move to, ultimately, bring processor development in-house for Silicon and to draw on their years of development with ARM architecture (no doubt drawing on innovations delivered by the consumed PA Semi staff and their pre-acquisition intellectual assets).

Then again, I’m a dork and am talking out of my exit port. 🤓
 

Longplays

Suspended
May 30, 2023
1,308
1,158
A design decision I wish Apple made with Intel Macs would be the removal of the DVI port & inclusion of the HDMI port during year 1 of Intel Macs starting in 2006 rather than in 2013(?).

HDMI ports should have never been removed from then until now.

This also applies with USB-A ports when USB-C ports were replacing Firewire & miniDP ports.

By now zero miniDP port and only one USB-A port should be present until year 2025.

2026 Macs would have no more USB-A ports at all.

People who need a built-in USB-A port can enjoy it on a 2025 Mac until the last macOS Security Update is released in 2035.
 
Last edited:
A design decision I wish Apple made with Intel Macs would be the inclusion of the HDMI port starting in 2006 rather than in 2013(?).

HDMI ports should have never been removed.

This also applies with USB-A ports when USB-C ports were replacing Firewire & miniDP ports.

I’m going to go out on a limb here and guess one reason Apple didn’t adopt HDMI from the outset was the HDMI standard at the start of the Intel transition, HDMI 1.2/1.2a, wouldn’t be able to drive Apple’s existing and current offering in the 30-inch Apple Cinema Display, which required both a dual-link DVI connection and a GPU able to deliver that output. HDMI version 1.4, which didn’t roll into use before 2009, would have been the first revision to accommodate the 30-inch’s 2560x1600 resolution (which is, interestingly, the same pixel resolution as the HiDPI display in a 13-inch rMBP).

Getting rid of other ports, like USB-A, was a mistake.
 

Longplays

Suspended
May 30, 2023
1,308
1,158
I’m going to go out on a limb here and guess one reason Apple didn’t adopt HDMI from the outset was the HDMI standard at the start of the Intel transition, HDMI 1.2/1.2a, wouldn’t be able to drive Apple’s existing and current offering in the 30-inch Apple Cinema Display, which required both a dual-link DVI connection and a GPU able to deliver that output. HDMI version 1.4, which didn’t roll into use before 2009, would have been the first revision to accommodate the 30-inch’s 2560x1600 resolution (which is, interestingly, the same pixel resolution as the HiDPI display in a 13-inch rMBP).

Getting rid of other ports, like USB-A, was a mistake.
Thank you for the explanation.

I was looking back to 2003 when HDMI products first came to market. Then wondered why Apple did not put it into Macs with year 1 of Intel Macs.

This is something I would have wanted to see with a 2003-2006 revision of the PlayStation 2, GameCube and Xbox 1 even at 480p or possibly 720p.

Making 2015-2020 Intel Mac laptops thinner than Apple Silicon Mac laptops is also a daft move too. Runs too hot, too slow and too short of a battery life was hell. The ideal port selection of 2013-2015 Macbook Pros is where it was at. Would have improved further if Apple used standard M.2 interfaces for their storage.

By now zero miniDP port and only one USB-A port should be present until year 2025.

2026 Macs would have no more USB-A ports at all.

People who need a built-in USB-A port can enjoy it on a 2025 Mac until the last macOS Security Update is released in 2035.

Would buyers of a mid-30s Mac even use a USB-A device?
 
  • Like
Reactions: TheShortTimer

TheShortTimer

macrumors 68040
Mar 27, 2017
3,249
5,639
London, UK
I was looking back to 2003 when HDMI products first came to market. Then wondered why Apple did not put it into Macs with year 1 of Intel Macs.

This is something I would have wanted to see with a 2003-2006 revision of the PlayStation 2, GameCube and Xbox 1 even at 480p or possibly 720p.

The GameCube is an interesting case - it was released with a digital AV output. When I bought mine almost 20 years ago this was highlighted in the manual but it would be a decade before I had a TV which was compatible with that type of signal.

Ironically the GameCube possesses superior video quality to its successor, the Wii.
 

Longplays

Suspended
May 30, 2023
1,308
1,158
The GameCube is an interesting case - it was released with a digital AV output. When I bought mine almost 20 years ago this was highlighted in the manual but it would be a decade before I had a TV which was compatible with that type of signal.

Ironically the GameCube possesses superior video quality to its successor, the Wii.
Because of the GameCube we bought a 2002 progressive scan TV that could display 480p via the GameCube's component RGB cables. Until recently those cables doubled in price in the eBay market.

2006 had us buying a 720p LCD TV that had a HDMI port.
 

salamanderjuice

macrumors 6502a
Feb 28, 2020
577
611
The PowerBook name wasn't even tied to PowerPC: we all know that the product line started with 68k processors.
Maybe Steve just disliked it due to being a very successful project being born under the Sculley era.
PowerBook i7? Steve would never have done it. That would've been the equivalent of putting an Intel sticker on it.
Coming from the guy that rebranded "AirPort" the WiFi standard and "SuperDrive" the DVD-RW tech.... not a chance.

Regardless of it, I'm silently praying for the PowerBook name to be revived when Apple will finally decide to make an hybrid Mac/iPad device.
Remember folks, you heard it here first.
SuperDrive was actually a reference back to the 68k days. The 1.44MB floppy drive of the time was called that since it could do 400k, 800k and 1.44MB discs in both Mac and MS-DOS formats. They've done similar things like with the iPhone version of "MagSafe" or "iBooks" on the iPad.

I think they just wanted "Mac" in all the product names and distance from the Power name despite some of those products pre-dating PPC.
 

salamanderjuice

macrumors 6502a
Feb 28, 2020
577
611
Thank you for the explanation.

I was looking back to 2003 when HDMI products first came to market. Then wondered why Apple did not put it into Macs with year 1 of Intel Macs.

This is something I would have wanted to see with a 2003-2006 revision of the PlayStation 2, GameCube and Xbox 1 even at 480p or possibly 720p.

Making 2015-2020 Intel Mac laptops thinner than Apple Silicon Mac laptops is also a daft move too. Runs too hot, too slow and too short of a battery life was hell. The ideal port selection of 2013-2015 Macbook Pros is where it was at. Would have improved further if Apple used standard M.2 interfaces for their storage.

By now zero miniDP port and only one USB-A port should be present until year 2025.

2026 Macs would have no more USB-A ports at all.

People who need a built-in USB-A port can enjoy it on a 2025 Mac until the last macOS Security Update is released in 2035.

Would buyers of a mid-30s Mac even use a USB-A device?
PS2, GameCube* and Xbox all supported 480p through their component cables. A decent number of Xbox titles even supported 720p and I know Gran Turismo 4 on PS2 can do 1080i (although I am not sure if it's truely rendering at that). No it's not digital and no it's not HDMI but it was a lot more common on consumer sets at the time. I was wowed by 720p Soul Calibur 2 on Xbox. I remember my parents new TV from ~2005/2006 had 1 HDMI port but 2 component inputs.

*Not all models, Nintendo weirdly likes to ruin video output during end-of-life revisions (see NES top loader, SNES Jr., Wii Mini).
 

Longplays

Suspended
May 30, 2023
1,308
1,158
PS2, GameCube* and Xbox all supported 480p through their component cables. A decent number of Xbox titles even supported 720p and I know Gran Turismo 4 on PS2 can do 1080i (although I am not sure if it's truely rendering at that). No it's not digital and no it's not HDMI but it was a lot more common on consumer sets at the time. I was wowed by 720p Soul Calibur 2 on Xbox. I remember my parents new TV from ~2005/2006 had 1 HDMI port but 2 component inputs.

*Not all models, Nintendo weirdly likes to ruin video output during end-of-life revisions (see NES top loader, SNES Jr., Wii Mini).
That is correct.

Initially those consoles supported 480p & better video standards via component cables but for retro gamers who want to play on current TVs with HDMI ports it would have been a great help to them that the last revisions were HDMI-only with a dongle for composite ports.

But then again people buying those hardware were looking for cheap entertainment. Those wanting cutting edge went with a PS3 & Xbox 360 with HDMI ports. Wii was positioned for the low-end so at most a component connector.
 
Last edited:

Amethyst1

macrumors G3
Oct 28, 2015
9,786
12,186
A design decision I wish Apple made with Intel Macs would be the removal of the DVI port & inclusion of the HDMI port during year 1 of Intel Macs starting in 2006 rather than in 2013(?).
HDMI first appeared on the 2010 Mac mini; then on the 2012 Retina MacBook Pro.

HDMI version 1.4, which didn’t roll into use before 2009, would have been the first revision to accommodate the 30-inch’s 2560x1600 resolution (which is, interestingly, the same pixel resolution as the HiDPI display in a 13-inch rMBP).
Prior to version 1.3/1.4 which supported 340 MHz pixel clock but didn't appear on GPUs before 2011/2012 (AMD Radeon HD 6000; NVIDIA GeForce GTX 600), HDMI was identical to single-link DVI (165 MHz pixel clock max), plus support for audio and HDCP. For monitors, replacing single-link DVI with HDMI <1.3 would have made zero difference/sense. And you can use a passive DVI-to-HDMI adapter to connect a HDMI TV to single-link DVI.

As @B S Magnet explained, the 30" Cinema Display requires dual-link DVI which cannot easily be adapted from/to HDMI. (There's a way that probably works but it's not straightforward.)

A much more significant and appreciated change (to/by me) was that the Intel iMac and MacBook had a DVI output and out-of-the-box support for extended desktop, unlike their PPC predecessors which only had VGA and only mirrored OOTB.

[...] the 30-inch’s 2560x1600 resolution (which is, interestingly, the same pixel resolution as the HiDPI display in a 13-inch rMBP).
That's probably just a coincidence. The HiDPI displays have four times the pixels of their predecessors for twice the pixel density, and the 13" MBP being 1280×800 meant it was quadrupled to WQXGA.
 
Last edited:

Amethyst1

macrumors G3
Oct 28, 2015
9,786
12,186
By now zero miniDP port and only one USB-A port should be present until year 2025.
There are cheap, passive adapters/cables to go from USB-C/Thunderbolt 3/4 to (mini)DisplayPort.

People who need a built-in USB-A port can enjoy it on a 2025 Mac until the last macOS Security Update is released in 2035.
People who need a USB-A port can use a very cheap, passive adapter to go from USB-C to USB-A. There's no use case that requires a built-in USB-A port AFAICS.
 

Longplays

Suspended
May 30, 2023
1,308
1,158
There are cheap, passive adapters/cables to go from USB-C to (mini)DisplayPort.


People who need a USB-A port can use a very cheap, passive adapter to go from USB-C to USB-A. There's no use case that requires a built-in USB-A port AFAICS.
The point was how the transition from all other ports to USB-C should have been handled by Apple.

Like retain HDMI from 2010(?) until today and future.

USB-A should only have 1 built-in port on all Macs by 2023.

People hate dongles. This becomes a problem when most users still use legacy ports. That was the challenge between 2016-2020 when Apple imposed USB-C on MBP users by killing off all the other ports.
 
  • Like
Reactions: B S Magnet

Amethyst1

macrumors G3
Oct 28, 2015
9,786
12,186
Like retain HDMI from 2010(?) until today and future.
The iMac and MacBook Air are the only current Macs that don't have HDMI. The MacBook Pro, Mac mini and Mac Studio use an active DisplayPort-to-HDMI converter to provide the HDMI (2.0) port which means that one of the GPU's DisplayPort connections is taken up by it, whether the HDMI port is used or not.
 

Longplays

Suspended
May 30, 2023
1,308
1,158
The iMac and MacBook Air are the only current Macs that don't have HDMI. The MacBook Pro, Mac mini and Mac Studio use an active DisplayPort-to-HDMI converter to provide the HDMI (2.0) port which means that one of the GPU's DisplayPort connections is taken up by it, whether the HDMI port is used or not.
I'm talking about the physical port to avoid unwanted dongles.
 

rampancy

macrumors 6502a
Jul 22, 2002
741
999
We also know PA Semi found new inroads with multicore PowerPC architecture, including 64-bit applications, but the principl customer to bail on PowerPC cosplayed a corporate amoeba and devoured PA Semi, leaving us with cryptographically locked/“paired” iPhones/iPads. :p
There was always this idea of the "great white hope" that would somehow save the PPC and/or the G4, and turn it into the übermensch platform we always knew it would become. There was the x704, then the 750VX, then the 7457-RM, then the 7500, then the 7448, and then PA Semi's remarkable PA6T-1682M.

I was going to say that most if not all of these chips either failed to make a convincing start/got cancelled, or never shipped in volume, but the faster 7457A and the later 7448 was all but ready to go, and the PA6T looks like it could have worked out for Apple, had they gotten a deal with Motorola/IBM to put it into production.

Between Apple crashing the AIM Alliance singlehandedly and Apple halting continuing development of PowerPC architecture by any serious start-up it could afford to swallow whole, the entire R&D to have have come to pass is, frankly, unknowable to any of us.
So this is the reason why I'm skeptical of this speculative future for the G4: Throughout the "500 Mhz" debacle with the original PPC 7400, and the subsequent "MHz Gap" of later revisions, it really seemed like Apple and Motorola struggled with scaling up the performance of the 74xx series...so much so that they tried many things – the "Megahertz Myth" marketing, the release of MP G4 systems, and the Xserve's system architecture – to work around that. What happened? Was the design of the G4 inherently problematic in developing further? Why was it seemingly so difficult to improve the bus speed, or the clock speed? Compared to the G3 and the 604 series, the G4 just seemed to be really troubled with its ongoing development.

I say this because I don't think the death of the AIM Alliance falls squarely on Apple's feet. The success of AIM depended on all three companies, with generally divergent core business interests, sharing the same general end goals. The problem is that they weren't: Apple wanted desktop and mobile general purpose computing CPUs to keep them competitive with x86, IBM wanted an platform for their "big iron" applications and Motorola seemingly wanted something to keep Apple as a lucrative customer for their semiconductor business, alongside their other customers. Put simply, I don't think IBM and Motorola genuinely wanted a powerful notebook/thin-and-light desktop-class PPC CPU as much as Apple did, especially if it didn't align with IBM's interests, or if it was too economically unfavorable for Motorola.

I think what would have really secured the future of the PowerPC is if Apple decided to buy out Motorola's entire PowerPC team and assets, purchased/licensed/shared what they also needed from IBM, and basically bring general-purpose computing PPC development fully in-house, contracting with IBM or Motorola (or later another company like Global Foundries or Samsung) to act only as fabs for their designs. Which I think might have made strategic sense after the G3, where we saw the first appearance of PPC silicon apparently custom-designed for Apple. Alas at the time Apple just wouldn't have had the money or resources to do that.

A best-case business outcome for Freescale would have been to the means to sell to Apple and third-party clones, as well as the embedded market. That, of course, never came to pass.
In retrospect, I think the whole clone program was set up to fail. Why did the clone manufacturers specifically target Apple's existing customer base, instead of going after Dell and HP/Compaq's customers? Why didn't Apple just fully implement all of the cool tech that the clone manufacters implemented in their designs, like Daystar's MP platform in their Genesis line, or Power Computing's dual-expansion bus design in the PowerWave series, or the CHRP motherboard in Motorola's own StarMax 6000?

If Apple had the resources, maybe what Apple could have done was subsidize companies like Power Computing to give them the support they needed to best compete against other companies in the low-cost x86 desktop market.


A bit ironic, once one considers how much of a retail pricing premium Macs commanded, even then, over their i386/x64 counterparts. As for the 7448, I’m not sure how this would have been a substantially more expensive CPU, owing to its refinement of an existing line which Apple had been using for roughly three years (or whenever the 7455 went on sale).
Here's where I admit I erred, in that I was thinking about the L3 cache-enabled 7457A, which apparently withered on the vine when Apple chose the 7447. I still feel that was not a good decision. Apparently the 7457A was more expensive to produce that the 7447 but its better performance would surely have made the extra expense worthwhile, especially if development of faster versions had continued.

The “G5” was never gonna make fetch happen on portables. IBM never designed the 970 for that use-case. This was Steve’s folly in picking favourites in the disintegrating AIM Alliance: that was a strategic gaffe in the pursuit of a tactical win.
In retrospect, I also think the 970 wasn't a good choice either. Whether or not Steve's argument for portables was a bad-faith excuse, the industry was clearly moving in the direction away from monolithic towers like the Power Mac to portables like the PowerBook and iBook. What Apple principally needed was a PPC chip designed from the ground up to be extremely power efficient while also being high performance, like what IBM was doing with the 750GX and 750VX.

(and the technical ability to engineer control over that software, even if he wouldn’t be alive to see that come fully to pass).
The other big factor here is Apple's historic obsession with controlling its own destiny. From their perspective, every time they've relied on another company for their platform to succeed, they've been let down due to technical ineptness, tardiness or misaligned interests. For better or for worse, they want full control over the whole widget.


Simplest won out, for worse or better. And once more, even more simple — by keeping it all internal — likely factored into Apple’s move to, ultimately, bring processor development in-house for Silicon and to draw on their years of development with ARM architecture (no doubt drawing on innovations delivered by the consumed PA Semi staff and their pre-acquisition intellectual assets).
I think that's exactly it. Instead of fighting with IBM and Motorola to develop competitive mainstream CPUs, why not just ally themselves with the company whose core business model is to develop competitive mainstream CPUs? And with the rise of ARM and the modern mobile market, it makes further sense to have taken the path of simplicity even further and just do everything in-house, which is something that I'm sure they could have tried to do in the post-68K era, if they'd had the resources and skills to do so.

Then again, I’m a dork and am talking out of my exit port. 🤓
Same goes for me! :D
 
Last edited:

AxiomaticRubric

macrumors 6502a
Sep 24, 2010
945
1,154
On Mars, Praising the Omnissiah
OP: I definitely know what you’re talking about here.

We had a Core Duo iMac. When it was eclipsed soon after in 2006 by the Core 2 Duo iMac it was a bit of a head-scratcher.

Maybe Apple wanted to test the marketing waters for Intel Macs before going all-in, or maybe it was very expedient due to an overabundance of Core Duo chips they could procure at low prices? We may never know for sure.
 

Longplays

Suspended
May 30, 2023
1,308
1,158
OP: I definitely know what you’re talking about here.

We had a Core Duo iMac. When it was eclipsed soon after in 2006 by the Core 2 Duo iMac it was a bit of a head-scratcher.

Maybe Apple wanted to test the marketing waters for Intel Macs before going all-in, or maybe it was very expedient due to an overabundance of Core Duo chips they could procure at low prices? We may never know for sure.
Steve wanted 64-bit chips for 2006 Macs. Intel had its own schedule.

Not having full control of your destiny end up having that bad compromise.
 
  • Like
Reactions: AxiomaticRubric

rampancy

macrumors 6502a
Jul 22, 2002
741
999
From the vantage of longtime folks on the PPC and EIM forums — ok, maybe just speaking for myself — this thread feels ever so slightly like a postmortem on Apple’s strategic decisions during their high watermark years.

Those cresting years are long behind them.
I think from the perspective of us grizzled old school veterans, perhaps -- but reading books like AppleDesign: The Work of the Apple Industrial Design Group or Apple Confidential is an interesting window on the ethos driving Apple. In a lot of ways, products like the AS MacBook Air is the pinnacle of Jobs' original vision for what the Mac was supposed to be: A "just works" appliance, fulfilling his "Mac in a book by 1986" ambitions, all entirely made in a process controlled from top to bottom by Apple.

Apple is always full of surprises. I didn't think Apple would release the eMac after going all-in on LCDs. I didn't think they'd even release something like the Mac mini, or the iPod shuffle.

Who knows? Maybe Apple will realize that modular electronics like Project Ara and the Framework Laptop are what will be the future, and we'll see MacBooks and iPhones that you really can build up like Lego. (With Apple making sure the "blocks" are proprietary and profitable to make and sell. :) )
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.