> There weren’t many 32 bit only Intel based Macs.
I don't understand, why Apple even created x86 osx ABI.
When they introduced the first x86 Macs, the writing was already on the wall; in the same way, that there are claims that Carbon was deprecated for years, x86 was in the door on its way out. You would not create a new Carbon-based app today, Apple introduced ABI in similar circumstances? Well, maintaining it then for decades to follow comes with the territory.
Yes, as an user, I do mind removing it. For example, Apple had broken Preview scanning on Samsung MFPs for the entire Mojave lifecycle ([1], [2]), there's no indication that they are going to fix it, and as a workaround, users are using Samsung Easy Document Creator, which talks directly to scanner, avoiding Apple scanner libs. Yes, it a 32-bit app.
When apple started their intel transition, intel used 32 bit CPU’s primarily. The first intel macs (core Duo) and intel dev kits were 32 bit, the core 2 duos onward were 64 bit. It’s really a small amount of Macs.
The previous gen, P4 and P-D were already 64-bit, XP 64-bit and 2003 64-bit was out, Linux was 64-bit for years; Core Duo not being 64-bit was a stop-gap and everybody knew that. Creating new ABI on that was exactly like launching a new Carbon project today, that's why I compared these two in the first place.
Nah. P4s, a gig of SDRAM, either a GMA 800 or GMA 900 for graphics, a 1x and a 16x PCIe slots, a 160GB disk and a DVD drive all running on the first Tiger service pack (10.4.1). Yours for 18 months for only $999! (‘Twas a rental.)
Late Pentium 4 in a pretty much random standard PC motherboard, I think it didn't even have EFI (even the broken 2001-vintage one that was common for years on x86 Macs).
I don't understand, why Apple even created x86 osx ABI.
When they introduced the first x86 Macs, the writing was already on the wall; in the same way, that there are claims that Carbon was deprecated for years, x86 was in the door on its way out. You would not create a new Carbon-based app today, Apple introduced ABI in similar circumstances? Well, maintaining it then for decades to follow comes with the territory.
Yes, as an user, I do mind removing it. For example, Apple had broken Preview scanning on Samsung MFPs for the entire Mojave lifecycle ([1], [2]), there's no indication that they are going to fix it, and as a workaround, users are using Samsung Easy Document Creator, which talks directly to scanner, avoiding Apple scanner libs. Yes, it a 32-bit app.
[1] https://discussions.apple.com/thread/8552818 [2] https://h30434.www3.hp.com/t5/Samsung/Scanning-problems-with...