Especially because Apple has a functional design which means there is nearly no redundancy; there's only one expert in any given field and that expert doesn't want to be stuck with old broken stuff. Nor does anyone want software updates to be twice as big as they otherwise would be, etc.
> Security was never a realistic excuse considering how much real zombie code still exists in macOS.
Code doesn't have security problems if nobody uses it. But nothing that's left behind is as bad as, say, QuickTime was.
nb some old parts were replaced over time as the people maintaining them retired. In my experience all of these people were named Jim.
> there's only one expert in any given field and that expert doesn't want to be stuck with old broken stuff.
Oh, my apologies to their expert. I had no idea that my workload was making their job harder, how inconsiderate of me. Anyone could make the mistake of assuming that the Mac supported these workloads when they use their Mac to run 32-bit plugins and games.
Not possible without forking the OS. No amount of money can make software development faster forever.
https://en.wikipedia.org/wiki/The_Mythical_Man-Month
Especially because Apple has a functional design which means there is nearly no redundancy; there's only one expert in any given field and that expert doesn't want to be stuck with old broken stuff. Nor does anyone want software updates to be twice as big as they otherwise would be, etc.
> Security was never a realistic excuse considering how much real zombie code still exists in macOS.
Code doesn't have security problems if nobody uses it. But nothing that's left behind is as bad as, say, QuickTime was.
nb some old parts were replaced over time as the people maintaining them retired. In my experience all of these people were named Jim.