9 ms·
> Yeah, it's a chicken-and-egg problem. You're not going to have any luck selling hardware which performs subpar with existing software Apple did it three time
by scarface_74 3y ago
> Yeah, it's a chicken-and-egg problem. You're not going to have any luck selling hardware which performs subpar with existing software
Apple did it three times with the Mac 68K -> PPC -> x86 -> ARM
- xattt 3y agoApple did a lot of backend work as well as developer shepherding in order to make that happen.
- scarface_74 3y agoAnd honestly Apple really only cares about its first party applications, Microsoft, Adobe and a few other high end applications. Microsoft has to care about niche vertical market apps that will never be updated.
- bee_rider 3y agoI’m sure Apple is the entity that caused the caveat. > Most vendors don't have the luxury of being able tailor both to eachother.
- scarface_74 3y agoI should have been more explicit. My comment was a supporting comment not a repudiation of what the parent poster said.
- rbanffy 3y agoI don't remember any cases of 68K software performing better on 68K macs than under emulation on PPC ones - parts of MacOS were still 68K code running under emulation until past the point booting MacOS on 68K was no longer possible. The same was true for x86 - by the time Apple started selling x86 machines, the x86's were so much faster than even G5's it was hard to notice any slowdown. And, while I assume there are uses in which some x86 MacPros still perform better than their ARM counterparts (1.5 TB of RAM must help), those are far and in-between.
- bell-cot 3y ago> I don't remember any cases of 68K software performing better on 68K macs than under emulation on PPC ones - ... There were situations: > The 603 was intended to be used for portable Apple Macintosh computers but could not run 68K emulation software with performance Apple considered adequate, due to the smaller processor caches. As a result, Apple chose to only use the 603 in its low-cost desktop Performa line.[12][13] This caused the delay of the Apple PowerBook 5300 and PowerBook Duo 2300, as Apple chose to wait for a processor revision. Apple's use of the 603 in the Performa 5200 line led to the processor getting a poor reputation. - from https://en.wikipedia.org/wiki/PowerPC_600#PowerPC_603 https://en.wikipedia.org/wiki/PowerPC_600#PowerPC_603 (The original PowerPC 601 had a 32KB unified cache, the problematic 603 had separate 8KB I- and D-caches, and the "problem-fix" 603e had separate 16KB I- and D-caches. My recollection is that the 68K emulation software was developed for and on the 601, and relied on some clever lookup and/or jump tables fitting into that CPU's large - for the time - L1 cache.)
- rbanffy 3y agoI think I had a 5200. I remember it not being a screamer, but certainly not slower than my IIci. I had them side by side for a while and both felt the same.
- bell-cot 3y ago"certainly not slower" while emulating a 68K system, or overall?
- rbanffy 3y agoOverall. I used Microsoft Word on both machines and IIRC, it was not a fat binary yet. It would probably feel slower than the top of the line 68040 models, but it was OK. It’s a shame I didn’t have A/UX on the IIci though (and don’t have the IIci anymore) but Unix didn’t look like it was the future at the time.
- scarface_74 3y ago